Jonathan Harris <jhar(a)tardis.ed.ac.uk> writes:
Please don't do that.
I was expecting this (however not for this reason).
The appropriate path on native Windows systems
doesn't include the lib/xemacs bit.
Why not. Where do the packages go under NT? Does it include just the
"xemacs/..." part
A brief note in the README advising
the user to unpack into lib/xemacs would probably be as good.
I really hate it when tarfiles unpack in more than one directory, it
also very annoying when you have to unpack the binary, the common and
the sumo tarball in different directories.
My feeling is that as long as XEmacs thinks bindir/../xemacs is
special we better make sure this exists. It is easier to persuade
capable people to just rename the tree if they need it somewhere
different.
Alternatively we could just unpack everything into some xemacs-bla.bla
directory and have the sysadmin move/copy the whole tree.
Jan