On Wed, 16 Oct 2002 23:29:11 +1000, Steve Youngs <youngs(a)xemacs.org> said:
Why don't you:
- Initially install the packages that you want via PUI and
*don't* do 'pui-add-required-packages' [1]
This of course assumes that I know what set of packages I *really* want...
(I'm playing devil's advocate here - there's nothing insurmountable here,
just a lot of headaches that take time - something that's always lacking ;)
To quote
http://www.xemacs.org/Documentation/packageGuide.html
" This is difficult to say. When in doubt, install a package. If you
administrate a big site it might be a good idea to just install everything. A
good minimal set of packages for XEmacs-latin1 would be
As mentioned before, an overview of existing packages and their purpose may be
found at ../Develop/packages.html and under the XEmacs source tree in etc/
PACKAGES.
xemacs-base, xemacs-devel, c-support, cc-mode, debug, dired, efs,
edit-utils, fsf-compat, mail-lib, net-utils, os-utils, prog-modes, text-modes,
time
Unfortunately the package system currently provides neither dependencies nor
conflicts. This will be a future enhancement. The above set includes most
packages that are used by others."
Hmm.. dangling list for latin1.. ;)
And if we don't do dependencies, what's this requires/provides entries in
the package-index file? ;)
Gnus requires w3, and w3 contains a require for emacspeak. Fortunately, it's
protected by an (if (featurep 'emacspeak), and it's not listed as a
'requires'
for w3 in the package-index. On the other hand, I don't see a listing for
emacspeak in the package-index at all (yes, I know it's not in the Sumos
either). But that's OK - it's an *optional* package and won't get sucked in
unless I want that, and the target goal was to only have the subset of stuff
that I want.
Meanwhile, a little ad-crock grep/tr/wc magic shows 53 different things listed
as 'requires' in package-index, and 1,237 'provides' listed. That's
really
confidence-inspiring - combined with the 'emacspeak' example above, it makes
me not trust the 'requires' list provided. Yes, I know the provides are on
the function level and the requires are packages - but now I get to worry
whether the aggregation was done right. Some spot checking, and we find that
mmm-mode requires xemacs-base and fsf-compat - but ibuffer requires *itself*
and xemacs-base. Tramp requires itself, text-modes doesn't. (Yes, I understand
why this is so - doesn't make it any less weird.. ;)
Screw this, it's time to just install the Sumo and pray. Score one for software
bloat. ;)
/Valdis