Oliver Graf <ograf(a)fga.de> writes:
What packages are considered core (i.e. should be inside a
'main' xemacs
distribution package),
The minimal number to get an automatic package fetching system to
work. That means right now it's basically `xemacs-base' and `efs'. A
Mule build requires `mule-base'.
and which are considered auxilliary (i.e. the installers choice)?
Everything else.
I'm currently writing a automatic package-get-base to rpm.spec
converted
(including correct and easy to use dependencies).
Cool!
I just wonder which package should go into the main tarball/rpm.
Don't mix packages with the XEmacs core tarball. Packages can be
updated after 'net release, the core cannot be until the next 'net
release.
Or should none? At least the mule-stuff for a MULE enabled package...
A case can be made for including `mule-base' since you cannot build
XEmacs/Mule without it.