* Julien Delange [Mon, 17 Oct 2005 02:30:35 +0200]:
Hi,
> > Was there a reason not to include amuleweb (and associated data
> >files)
> > in the amule-daemon package? As I understand it, the package is
> > unusable now, since there is now way to control the daemon by only
> > installing the amule-daemon package. This could warrant a grave bug.
> > What's your opinion on this?
> I think that the slitting is actually not complete. I'm aware of that.
> But I don't have enough time, and I will take my new appartment in a
> week, so, I will have more time in a few days.
> I think the best thing is :
> - one package amule-utils, which is actually the same as the current
> - one package amule-webserver which contains webserver for amule
> - one package amule-daemon which contains only the daemon
> - one package amule which contains the complete GUI
> But I don't know if I can make a such split. I will test as soon as
> possible. It's may be possible to package a new package called
> amule-data to put .po files and other data like icons, ... This
> decision needs test and I will do it as soon as possible.
I've been thinking for this issue for a while, and one option that has
occurred to me lately, which in my view provides the benefits of
splitting the package, and avoids the disadvantages of a split
involving more than two packages, would be:
Package: amule-nox
Package: amule
Depends: amule-nox (= ${Source-Version})
Where amule-nox will contain _everything_ that does not need X
libraries, that is, everything except /usr/bin/amule and
/usr/bin/amulewebDLG.
* * *
Because, come on, there is not much point on splitting things in 4 or
5 separate packages. A user will either want amule installed, or not
installed; and the single scenario I can think of where a split would
be useful would be not wanting to install X libraries (e.g., on a
server). This is, BTW, a quite common reason to make a split in
Debian.
* * *
As for the name, -nox is the suffix one normally uses in this
circumstances, although I'll admit that amule-daemon may provide more
information to the users. Still, is a decision to make, whether to use
the consistent-but-less-user-friendly amule-nox, or the inconsistent
(because it'll contain other things than the daemon) but-more-useful
amule-daemon.
* * *
With my Debian Developer hat on, I strongly advice against splitting
this package in more than two packages, and strongly suggest that the
amule-daemon or amule-nox package can be fully operational by itself,
which at the moment is not.
The rationale against more than two binary packages is that in this
case, the split does not happen because of size issues (e.g., to allow
different independent parts, which are veeery big, to be installed
independently, or to save mirror space by putting arch:all files in a
separate -data package), but only to avoid the big dependency chain
that the X libraries are.
Cheers,
--
Adeodato Simó
EM: dato (at) the-barrel.org | PK: DA6AE621
Guy: My dad made my mom have a cesarean when she had my little brother.
He wanted to make sure he was born in the 1986 tax year so he could get
another tax credit.
-- http://www.overheardinnewyork.com/archives/002968.html
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
