Re: Test suites after build and Build-Depends.
- To: email@example.com
- Subject: Re: Test suites after build and Build-Depends.
- From: Charles Plessy <firstname.lastname@example.org>
- Date: Sun, 1 Feb 2009 10:16:04 +0900
- Message-id: <[🔎] 20090201011604.GF13843@kunpuu.plessy.org>
- In-reply-to: <email@example.com> <20090131121018.GB8148@codelibre.net> <20090131091515.GA11879@rivendell>
- References: <firstname.lastname@example.org> <20090131121018.GB8148@codelibre.net> <20090131091515.GA11879@rivendell>
Le Sat, Jan 31, 2009 at 10:15:15AM +0100, Raphael Hertzog a écrit :
> Note that this decision has been taken because:
> - dpkg-source has never used debian/substvars as input and did nothing
> unless you gave the -T option
> I hope my answer clarifies the situation. Given that it has not been used
> in 14 years, and that we had no wishlist bug in that direction, it seems
> pretty clear that it's useless and that there are other better ways to
> achieve similar functionnality.
Le Sat, Jan 31, 2009 at 12:10:18PM +0000, Roger Leigh a écrit :
> The .dsc file is exactly where the information is read from. See
> fetch_source_files() in Sbuild/Build.pm. This is for installing
> and removing build-dependencies and build-conflicts, respectively.
> Note that dpkg-buildpackage and other tools read debian/control
> to check that the build-deps are satisfied in addition.
Thank you all for your answers,
from my biologist point of view, I find interesting to observe how an unused
function progressively becomes impracticable as the whole system evolves
without pressure to stay compatible with it :) Helper tools such as
mk-build-dep have not been mentionned in this thread, but would also break with
packages containing a substvar in debian/control.
I can try prepare a patch for the Policy if you are interested.
Have a nice Sunday,
Tsurumi, Kanagawa, Japan