>>>> Stephen J Turnbull <stephen(a)xemacs.org> writes:
What we really want to do here is install any packages that come
with the source code in the right place and go from there.
This assumes the source is newer than the packages. Blindly installing
the bootstrap packages from the source might be a bad idea.
The complexity is entirely due to the fact that for historical
reasons packages might be anywhere in the user's system, and that
XEmacs has changed its default location for package installation,
but the users are going to expect that previously installed packages
will be found and used.
Maybe we need to limit the scope of what improvements we are trying to
do? It seems like the general case of working perfect under all
circumstances could be hard to tackle at least now. I can't see
through all the twisty little maze of packages anyway!
My original goal was to make the package system work so that a user
could install the binary, from source or from an installer, and go on
from that using what is built in For mercurial or tar-ball-users it
might be solved with an option to configure or a make target!?
More useful is maybe to address the issue with when a user is on an
existing installed system and wants to update or install new
packages. This ought to be of benefit for many users.
That use case might actually work out of the box. Building everything
from sources has kept me away from that use case almost entirely.
However when I just tried it it did fail. First obstacle. I didn't
have ftp on my path. I fixed that but then getting the package list
turned into an endless loop somewhere. I guess this would make most
users give up on the idea of using the package system. I'll see if I
can get past this point some how and see what other problems might
 I actually assumed there would be no previous packages installed
in this scenario but its usefulness might be to limited!?
XEmacs-Beta mailing list