Updated. Update to 2.13.0.8 and use EXPANDED_DATADIR instead of %{datadir}

2006-02-13  Brian Cameron  <brian.cameron@sun.com>

        * Release 2.13.0.8:
        * NEWS: Updated.
        * configure.ac: Update to 2.13.0.8 and use EXPANDED_DATADIR instead
          of %{datadir} since that makes it work much better.
        * README.install, README, docs/C/gdm.xml:  Update docs so that the
          change from --with-configdir to --with-defaults-conf and renaming of
          default and custom config file is documented.
        * daemon/gdm-net.c, daemon/gdmconfig.c, gui/gdmsetup.c: Update comments
          to no longer mention old name of config file.  Fix gdmsetup to know
          new location of custom config file.
        * config/Makefile.am: Now if upgrading and gdm.conf and
          factory-gdm.conf are different, move the gdm.conf file to
          custom.conf instead of copy.  This is  because we don't want GDM
          to overwrite the custom.conf file every time user upgrades.  Only
          first time, then gdm.conf should go away.

1 files changed, 4 insertions, 4 deletions

diff --git a/README b/README
index f3178a8d..7213e231 100644
--- a/README
+++ b/README
@@ -83,10 +83,10 @@ Reporting Bugs:
      http://bugzilla.gnome.org/
 
   When reporting bugs you should first turn on debugging on the
-  "Security" tab of gdmsetup or editing gdm.conf-custom as
-  described in the documentation.  This causes debug messages to
-  be sent to the system log (/var/log/messages or /var/adm/messages)
-  and include the GDM output sent to syslog.
+  "Security" tab of gdmsetup or editing custom.conf as described in
+  the documentation.  This causes debug messages to be sent to the
+  system log (/var/log/messages or /var/adm/messages) and include
+  the GDM output sent to syslog.
 
   You should not have to configure syslog for this to work, but if
   you do not see GDM messages in your syslog it may require