Re: Packaging problem.
On Tue, 6 Jan 2004, Jean-Michel Kelbert wrote:
> Le 06/01/04 à 13:32 Tomas Pospisek's Mailing Lists (tpo2@sourcepole.ch) écrivait :
> > Having a lib only makes sense when and if there are other packages using
> > it. Are there any? Basing your decision on the _doctrine_ that libs should
> > be packaged separately isn't a very good idea: the same doctrine could be
> > applied to -doc and -i18-some-language. Applied universally this would
> > result in a major pain for admins.
>
> I don't see the problem for admins : there is depends/recommends...
It is a problem. Debian has too many packages _now_. apt-get update is
sluggish allready. Navigating through 10'000 packages as well. Etc.
> It is better to separate, when it can be usefull.
In theory yes. But theory is not practice. A package can depend on k3b and
then it has everything it needs.
> Do you imagine you want kde in German, and you have to all kde-i18n
> languages...
Sure, you need to balace to pros and the cons of splitting a package.
Sometimes it makes sense, sometimes not.
> For the moment no others programs use k3blibs, but it can change, and it
> is better to have the separation now.
I suggest you split it once the fact it's splitted is useful. Now it's
_not_ useful since no other package depends on it.
> By the way, it would be interested to determine how many libs are used
> by only one package.
You can determine that: reverse-depends. But do you think the argument
"others have done it as well" would be useful?
*t
--
-----------------------------------------------------------
Tomas Pospisek
http://sourcepole.com - Linux & Open Source Solutions
-----------------------------------------------------------
Reply to: