Re: Is declaring correct deps/conflicts for versions not in stable really no longer needed?
- To: email@example.com
- Cc: Adam Conrad <firstname.lastname@example.org>
- Subject: Re: Is declaring correct deps/conflicts for versions not in stable really no longer needed?
- From: Jeroen van Wolffelaar <email@example.com>
- Date: Tue, 12 Oct 2004 12:08:03 +0200
- Message-id: <20041012100803.GU13669@A-Eskwadraat.nl>
- In-reply-to: <firstname.lastname@example.org>
- References: <email@example.com> <firstname.lastname@example.org> <20041012093319.GV18918@A-Eskwadraat.nl> <email@example.com>
On Tue, Oct 12, 2004 at 02:03:00PM +0400, Nikita V. Youshchenko wrote:
> This depends on point of view.
> If a library < X.Y does not provide a feature needed by a package, it's a
> common practice to make package depend on library (>= X.Y). Other
> packages, that don't need that library feature, don't need to depend on
> library (>= X.Y).
> The case with libapache-mod-php4 / glibc looks similar: glibc less than
> 2.3.2.ds1-17 does not provide neede functionality [due to a bug]. This
> affects libapache-mod-php4, but does no affect most (all?) other packages.
So, lacking a bug is a feature?
I always thought bugs were features...
Jeroen van Wolffelaar
Jeroen@wolffelaar.nl (also for Jabber & MSN; ICQ: 33944357)