On 23 Mar 2002, Stephen J. Turnbull said:
You should need only one copy of the packages.
... saving things like incompatible byte-compiler changes (which
fortunately happen *very* rarely).
David> Personally, I'd just as soon move this up to
David> /usr/local/xemacs/xemacs-v.e.r and leave the /lib/ out of
David> it. But tradition is tradition.
On Linux it's actually a published standard.
As well as being the only halfway sane way to do this sort of thing. If
you want to organize by packages, use GNU stow and prefix= at install-
time.
(Or GNU stow and prefix= *and* exec_prefix= at install-time, as I do at
one of the more disk-space-starved sites at which I keep an XEmacs.)
David> I also have persistant problems with auto-autoloads
that
David> are "already loaded." I've commented on that but I'm
told
David> it's a "normal" bug.
This is _not_ normal. One possible cause is load-path shadows. M-x
list-load-path-shadows. Another possibility is a package that
contains a file that's also dumped into XEmacs. There may be others.
The one I normally see is that I organize my sitewide lisp into packages
with names similar to the XEmacs ones, and then the auto-autoloads file
generated by `batch-update-directory' gives the autoloads files feature
names the same as ones already used for non-site-specific XEmacs
packages.
(It's easily fixable by editing the auto-autoloads files by hand, and
because batch-update-directory edits the auto-autoloads files rather
than rewriting them, that only has to be done once...)
--
`Oh, I seeeee, good light; bad light. Presumably the bad light is
different -- perhaps it's a sawtooth waveform, and the pointy bits
scratch your eyes?' --- John Ineson to a `monitors emit radiation,
all radiation is bad, therefore monitors are bad' tub-thumper