Re: mass-commit: dependencies
Dominique Dumont <firstname.lastname@example.org> writes:
> On Friday 06 July 2012 01:17:47 Jonas Smedegaard wrote:
>> c) is almost harmless and needless: Yes, Joey instructs to do so but
>> really a dependency on debhelper 7 is implicitly satisfies as no older
>> version is provided in any currently supported release of Debian. APT
>> dependency resolving is already plenty burdened - we really should work
>> actively to _reduce_ needless versioned dependencies.
> IIRC, lintian complains if the dependency on debhelper is not
> versioned.  I'll happily remove this feature if I'm wrong.
It was lowered to a pedantic tag. Whether you want to keep it given that
is a judgement call. I always maintain that dependency on all of my
packages. I've never seen any sign that this dependency caused problems
for apt during installation of build dependencies, and since it's only a
build dependency, it doesn't make it into the final package.
N: The package either doesn't declare a versioned build dependency on
N: debhelper or does not declare a versioned build dependency on a new
N: enough version of debhelper to satisfy the declared compatibility
N: Recommended practice is to always declare an explicit versioned
N: dependency on debhelper equal to or greater than the compatibility
N: level used by the package, even if the versioned dependency isn't
N: strictly necessary. Having a versioned dependency also helps with
N: backports to older releases and correct builds on partially updated
N: Refer to the debhelper(7) manual page for details.
N: Severity: pedantic, Certainty: certain
N: Check: debhelper, Type: source
Personally, I would recommend keeping it, but IIRC Jonas and I have had
this argument before. :)
Russ Allbery (email@example.com) <http://www.eyrie.org/~eagle/>