[Spambayes-checkins] spambayes WHAT_IS_NEW.txt,1.23,1.24

[Tony Meyer]

Update of /cvsroot/spambayes/spambayes
In directory sc8-pr-cvs1:/tmp/cvs-serv21286

Modified Files:
	WHAT_IS_NEW.txt 
Log Message:
Well, it's been some time, and no-one disagreed, and three people liked the idea,
so here it is.

MAY BREAK THINGS!

>From now, path/file options are not relative to the current working directory,
they are relative to the last configuration file loaded.  This still defaults to the
current working directory (except on Windows with win32all, where it's still
the User Application Data directory).  So this should mean no noticeable change,
unless your last configuration file is not in the current working directory, and
your data is.

Index: WHAT_IS_NEW.txt
===================================================================
RCS file: /cvsroot/spambayes/spambayes/WHAT_IS_NEW.txt,v
retrieving revision 1.23
retrieving revision 1.24
diff -C2 -d -r1.23 -r1.24
*** WHAT_IS_NEW.txt	29 Dec 2003 04:46:31 -0000	1.23
--- WHAT_IS_NEW.txt	12 Jan 2004 08:36:14 -0000	1.24
***************
*** 17,21 ****
  --------------------------
  
!  o XXX
  
  There should be no other incompatible changes (from 1.0a7) in this release.
--- 17,32 ----
  --------------------------
  
!  o The way pathnames in option files are handled has changed, as has the
!    default values for some pathname options, in some situations.  All
!    pathnames in option values that are not absolute (with Windows, this
!    means they will start with a drive letter) are now relative to the
!    directory of the last configuration file to be loaded, rather than to
!    the current working directory.
! 
!    What does this mean for you?  Nothing, as long as your pathnames
!    (the cache directories and databases, primarily) are either absolute
!    or in the same directory as your configuration file.  If, after
!    upgrading, your database is suddenly empty, then you need to fix your
!    configuration so that it points to the correct place.
  
  There should be no other incompatible changes (from 1.0a7) in this release.