On Tue, Oct 04, 2005 at 07:59:40PM +0200, Frank Lichtenheld wrote: > On Tue, Oct 04, 2005 at 03:50:34PM +0200, Denis Barbier wrote: > > In order to prevent false positives, checks have been added to > > checks/po-debconf to see if the package depends upon debconf. > > This is done by parsing debian/control, but nowadays this > > dependency is pulled in by ${misc:Depends}, so checks/po-debconf > > stops before running its own checks, which makes checks/po-debconf > > pretty useless. > > Indeed. I see no simple solution that supports both purposes, though.
Neither do I. Maybe debhelper should not depend on po-debconf so that maintainers have to add an explicit dependency on po-debconf. > Will try to come up with something but any suggestions welcome... My only idea is to check for config scripts, something like : In debfiles, if there is a file m/^(.+\.)?templates(\..+)?$/ and there is also a file m/^(.+\.)?config(\..+)?$/ then $has_template=1 Please note that some templates and config file are preprocessed, thus their name is templates.in, templates.master or config.in Denis -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]