Hey On Sun, Jun 28, 2009, Josselin Mouette wrote: > I’m attaching a new debhelper script named dh_devlibs. As the name says, > it is meant for development libraries.
Thanks on working on this new tool! > Currently it does two things: I wonder whether it's a good idea to mix handling of *.la and *.pc; perhaps you should split that in two helpers or allow disabling either support via command-line flags so that package maintainers can opt to use this or that feature on this or that package. > * Generation of a dev:Depends dependency field, based on the > contents of pkg-config files. This will remove the need to check > which build-dependencies also need to be -dev dependencies, and > to keep the versions in sync. I read quickly through the script and wondered aboud a couple of things. * I wondered whether parsing of Build-Depends could be done in a common Debhelper control file parsing function, or even in dpkg-dev * the behavior to use either Build-Depends (Debian specified) or .pc versions (upstream specified) is not controllable; I wonder whether only one behavior should be implemented. My personal wish would be to use a similar system for .pc than shlibs: packages shipping .pc files would provide a minimum version to depend on and that's what we would use. Perhaps taking the highest of this version and the bdep could be offered as a flag? Thanks! -- Loïc Minier -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
