Re: Automatic Debug Packages
On Mon, Aug 10 2009, Philipp Kern wrote:
>> Why is it not trivial? I have such a hook in my pakages, and it
>> is not rocket science.
>>
>> If you think that adding stuff like
>> --8<---------------cut here---------------start------------->8---
>> file lib_or_exec_file
>> objcopy --only-keep-debug lib_or_exec_file debug_file
>> objcopy ----add-gnu-debuglink debug_file lib_or_exec_file
>>
>> strip --remove-section=.comment --remove-section=.note \
>> --strip-unneeded lib_file
>> strip --remove-section=.comment --remove-section=.note exec_file
>> --8<---------------cut here---------------end--------------->8---
>>
>> to a rules file is "not at all trivial", then heaven help us.
>
> Plus lines to actually create the package with appropriate control info
> or/and putting it into debian/control which we wanted to avoid (I think).
>
> Of course if we then go and try to modify the behaviour slightly (like
> having build-ids and stuff) we still have to modify all those packages
> and not just the helper and a binNMU. But I guess I can't argue with
> you about that anyway. From a policy PoV you're right, we do not
> impose debhelper upon everyone.
>
> I already consider debhelper coverage as a worthy goal. :-P
Oh, it is a wonderful goal. But anything we put into policy
should not just depend on debhelper being the only route to get the
advantage of debug packages; there should be enough information in
there where a packager (or developer of a helper package) can create
policy compliant debug packages.
I have never objected to having debhelper auto-create debug
packages, I just object to putting things in policy that say "Use
debhelper or python-central to create these policy compliant
packages". Policy ought to deal with specifying the package naming
convention and the contents, not specifying you get whatever the tool
shall produce.
manoj
--
"We all know Linux is great...it does infinite loops in 5 seconds."
(Linus Torvalds about the superiority of Linux on the Amsterdam Linux
Symposium)
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/~srivasta/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Reply to: