>>>> Stephen J Turnbull <stephen(a)xemacs.org> writes:
Thanks for a long reply. I think I need to take it piece by piece to
digest it. There seems to be rally a lot to consider here. I feel
partially lost. Different use cases. Different requirements. First
part up for discussion.
There is also some beginning support for including a tarball of
packages in the source tarball (etc/bundled-packages/). [...]
Unfortunately, the packages *do* need to be installed, so that's
something we can really get around.
OK. We need to get the basic packages in somehow to bootstrap.
It would be a real disservice to users if they got multiple
installations of packages, especially if some are "full" and others
are bootstrap ("crippled" for normal use). Basically, what needs to
be done is to come up with a reasonable list of places where
packages *might* be installed.
Couldn't the bootstrap packages just be available for the package
system? If user can install the binary why not install the bootstrap
packages with it but only use it for the package system? (A lot like
having curl in core for downloading the packages.)
The normal case for bootstrapping would also be when there are not
packages available!? If the distro or user himself has downloaded the
full packages we need not bother about the bootstrapping. In that case
we are talking more about what the package system should do when there
is full tree already available.
XEmacs-Beta mailing list