Re: Build-deps on buggy packages.
On Fri, Aug 03, 2001 at 07:44:39AM -0500, Colin Watson wrote:
> On Fri, Aug 03, 2001 at 01:31:34PM +0200, Daniel Kobras wrote:
> > But what about package foo? Should I re-upload with
> > Build-Depends: bar (>= fixed-version), being nice to porters/auto-builders
> > at the cost of people who might try to build my package from source on,
> > say, a woody system with an earlier (and perfectly working) version of
> > bar? In other words, should I use versions in Build-Depends to reflect
> > source-level or packaging-level dependencies? While the former seems to
> > be more appealing at first sight, how do I tell folks "but don't build
> > against version x.y.z of bar because it's known to be buggy, and don't
> > bother filing my bugs about it"?
>
> 'Build-Conflicts: bar (= x.y.z)'?
Makes it look a little nicer as long as only one version/revision of bar
is affected. It doesn't prevent unnecessary builds/uploads though. And it
doesn't really answer the question whether foo should have to care about
packaging bugs in bar. Imagine bar == libc, shall we put
Build-Conflicts: libc (= a.b.c) in just about any package?
Regards,
Daniel.
Reply to: