Regarding the overwriting of user-edited packages, first just the 2 we
need to do,
and then the rest.
Add some intelligence to the installer,
maybe by having some lisp code do the installing instead of a tar file.
shell scripting might work as well(?)
Something like this:
-First get info about what is already there
-the path used in the XEmacs install for the package directory.
-if either of the two files we are installing (efs, base) exist in
-Check if they exist elsewhere.
-look for filename
-double check by looking inside that file for version/signature
-Report what we find,
-if these two packages are not found
present to user where you plan to install
-user supplied path?
-for each of the 2 packages (base and efs),
if package is found
rename old packages and install new?
-Install 2 files
-find the downloaded files
uncompress and install them to the path
-Report to user
-what was installed
-where we put it.
Something like this might avoid the problems of overwriting a user-edited
efs or xemacs-base, should that ever exist.
A separate problem is overwriting the rest of the packages if users have
indeed edited other packages.
Maybe the package manager itself could be modified so
if replacing a package,
either prompt to:
-backup old package by renaming
-overwrite old package
-skip this package,
go to next package if there is one selected to install
The above is not exact flow, just a general idea.
XEmacs-Beta mailing list