Hrvoje Niksic <hniksic(a)arsdigita.com> writes:
>> > Building at installation time would be preferred,
>> Fully agreed.
> IMHO it's not that clear. Today, XEmacs =users= are installing
> packages. Not the administrator.
Is that your experience? From what I see, the administrators are
usually expected to set up XEmacs, which they do by downloading the
The users who care to download individual packages seem to be the
minority of experts. Maybe things will be different in several years,
but that's how I see things "today."
You're right. I think the /intention/ is for users to install the
packages though (why take up the menubar with it otherwise). If
everyone is happy with download SUMOs, why bother with packages? /I/
do think packages add a value, but maybe it takes a while until more
people realize it.
> IMHO using `rpm' or any other well-known packaging tool, that
> already went through all these problems and solved them, would be
Far from nice, I'm afraid. Using a generic packaging tool like RPM
wouldn't really solve the problems, it would just move them to a new
level, one I'm not sure we want to handle.
Yup. But perhaps some other projects have the same headaches, and
will work on solving them in rpm/deb. A proprietary packaging system
takes time to maintain and wouldn't be reusable in other projects.
Also, users aren't familiar with it.
Some of the problems I see are:
* Whichever solution we choose will be unusable by many users. I, for
one, use Debian and don't want XEmacs to spawn `rpm' with its entire
Maintaining both .deb and .rpm isn't impossible. I would imagine
debian/redhat people would be interested in helping maintain these as
The current system has a problem on Debian/RedHat, updating any
package within XEmacs breaks the rpm/deb database.
* Does RPM even run on Windows?
Does Cygwin count as Windows? If so, yes.
But to be consistent, I would say that XEmacs should use the Windows
packaging system under Windows instead of using a proprietary system
most users aren't familiar with. OTOH, the windows packaging system
is probably even worse than deb/rpm. OTTH, must XEmacs windows users
are probably Cygwin users anyway, so they should be used to the Cygwin
installer (but perhaps that doesn't do updates..).
* Managers like RPM and dpkg are way too complex for what we need,
yet are woefully inadequate when it comes to solving problems we
have. We need user-installable packages, installing packages in
different locations, support for multiple XEmacs versions on the
Rpm/deb should handle this, I think. It's just tar/cpio/whatever with
a fancy interface, you can unpack it everywhere.
Maybe we've had this discussion before though...