Bug#649784: On dh_apparmor, and possibly other dh_* stuff in the future

2012-01-09 Thread Gergely Nagy
Kees Cook k...@debian.org writes: On Wed, Dec 28, 2011 at 11:23:28AM +0100, Stefano Zacchiroli wrote: But still it'd be useful to have such a package for dh_* scripts that have no obvious location. If Joey has no objections, I believe you should just go ahead creating debhelper-extras (or

Bug#649784: On dh_apparmor, and possibly other dh_* stuff in the future

2011-12-28 Thread Stefano Zacchiroli
On Wed, Dec 28, 2011 at 12:01:04AM +0100, Gergely Nagy wrote: Yup, this is the reason I dared raising the option in the first place. (Though, even if this weren't the case, I'd be up for helping maintain such a package, but thankfully, doing so would be an easy job.) So, if I understand it

Bug#649784: On dh_apparmor, and possibly other dh_* stuff in the future

2011-12-28 Thread Gergely Nagy
Stefano Zacchiroli lea...@debian.org writes: Then we only need a package name, possibly finding other scripts apart from dh_apparmor (perhaps even poking the maintainers of various dh_* scripts if they'd consider merging into a single thing), and a maintainer (I'm willing to help with that,

Bug#649784: On dh_apparmor, and possibly other dh_* stuff in the future

2011-12-28 Thread Kees Cook
On Wed, Dec 28, 2011 at 11:23:28AM +0100, Stefano Zacchiroli wrote: But still it'd be useful to have such a package for dh_* scripts that have no obvious location. If Joey has no objections, I believe you should just go ahead creating debhelper-extras (or whatever name pleases you),

Bug#649784: On dh_apparmor, and possibly other dh_* stuff in the future

2011-12-27 Thread Gergely Nagy
Hi! As I mentioned earlier[1] in the bugreport, I had to work with more than one package that could've used dh_apparmor, and that's at least one too many for my taste. So I've been thinking about a way to resolve this situation, and - if possible - avoid similar issues in the future, without

Bug#649784: On dh_apparmor, and possibly other dh_* stuff in the future

2011-12-27 Thread Kees Cook
Hi Gergely, On Tue, Dec 27, 2011 at 04:03:00PM +0100, Gergely Nagy wrote: We could start with dh_apparmor (since packaging a single tool like that separately does not make much sense to me), and add others as the need arises. What do you all think? If the ABI of the dh_* tools is

Bug#649784: On dh_apparmor, and possibly other dh_* stuff in the future

2011-12-27 Thread Joey Hess
Kees Cook wrote: If the ABI of the dh_* tools is considered stable and exportable, I have no problem with this. If debhelper will change its ABI in the future, then this separate package is going to be a pain to maintain. Debhelper has had a stable, documented ABI for 12+ years; there are

Bug#649784: On dh_apparmor, and possibly other dh_* stuff in the future

2011-12-27 Thread Gergely Nagy
Joey Hess jo...@debian.org writes: Kees Cook wrote: If the ABI of the dh_* tools is considered stable and exportable, I have no problem with this. If debhelper will change its ABI in the future, then this separate package is going to be a pain to maintain. Debhelper has had a stable,