Re: Policy about packages that have Tk dependent parts.
Philippe Troin <email@example.com> writes:
> > Philippe Troin <firstname.lastname@example.org> writes:
> > > Two packages instead of one. We have 1400+ packages in main (around 2000
> > > including non-free and contrib), and I think we should apply care when
> > > creating new packages especially when the foo-tk package is likely to be
> > > a few kilobytes.
> > Why is it a bad thing in itself to have more packages, even if we have
> > a lot of them?
> Well, if you find it easy to nagivate through 2000 packages, will all the
> current mess of lib-g, altdev, devs, then it's ok for me.
I understand your sentiment, but my feeling is that adding the
additional package is probably not a big deal. The names will be
closely related, so it should be obvious what they're for.
Not creating the two packages won't solve our problem with package
count overload; for that we need a more general solution because we
*will* keep getting more packages. Last I heard, the diety project
was working on addressing this issue.
Rob Browning <email@example.com>
PGP fingerprint = E8 0E 0D 04 F5 21 A0 94 53 2B 97 F5 D6 4E 39 30