On Tue, 30 Dec 2008 09:23:44 -0800 Russ Allbery <rra@debian.org> wrote: > Lintian actually isn't confused at all. It's behaving as designed. > Whether that design is correct in this case is another question, though. > > dpkg-dev depends on make and Recommends build-essential. > > > I appreciate this is an unusual situation, but could dpkg-dev be > > accepted by lintian as providing the relevant interpreter for > > debian/rules when installed in /usr/share/ ? > > That being said, I can see the argument that you're not calling make > directly; the package itself only uses dpkg-buildpackage. Also, given > that the defined build interface for a Debian package is make, it's hard > to imagine dpkg-dev ever *not* depending on make. With this particular package, if there was a way of using dpkg-buildpackage *without* using make (e.g. just using /bin/sh) , it would probably use it. The packaging itself is almost completely trivial, what matters is that the package is Priority: required (so that debootstrap picks it up without changes) and that it meddles with files from other packages in non-Policy ways (so it cannot be uploaded to Debian and has to be generated on-the-fly). > However, before I make that change, one question: why are you depending on > dpkg-dev instead of build-essential (which Lintian would already respect > and which is the more standard way of getting all of the tools required to > build a Debian package)? Is it because you don't want the compilers? Yes, the package is Architecture: all and does not need compilers of any kind. grip-config is (and will stay) a config package that merely does weird things with configuration files and directories. I haven't even migrated the postinst to perl yet. ;-) -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
Attachment:
pgpxDFuncvcy5.pgp
Description: PGP signature