Re: dh_strip and -X
On Thu, Jan 17, 2002 at 12:12:04PM -0600, Steve Langasek wrote:
> On Thu, Jan 17, 2002 at 05:43:37PM +0100, Stefano Zacchiroli wrote:
>
> > > So, don't use dh_strip. dh_strip is a simple tool for simple
> > > configurations; if you have one binary you need stripped, and one binary
> > > you need left alone, and dh_strip doesn't do the trick, call strip
> > > yourself.
>
> > > strip --remove-section=.comment --remove-section=.note path/to/foo.opt
>
> > Yes, this is the obvious solution, but if someone will change the
> > behaviour of "standard" debian stripping (e.g. add another
> > --remove-section argument) I have to change my "strip" invocation.
> > That's it.
>
> > BTW, this is a shared problem between all debhelper programs that
> > support "-X" flag (I think almost all), why does not exists the
> > possibility to use a list of file that have to be stripped like a
> > debian/strip file?
>
> Oh, well, if you think debhelper needs improving, you can always submit
> a patch. :) But until your patch is included, calling strip by hand is
> the only way to have a policy-compliant package.
>
> Incidentally, is there a reason that the bytecode version stores
> important information in the sections that are stripped? It seems to me
> that this is a bug in the package's build sequence or in the compiler.
> Or is it a file format that can't be stripped, which dh_strip is trying
> to act on anyways (which would be a bug in debhelper)?
Well, yes, we can try to identify such files, and if it is possible for
debhelper to not sstripe them, i would be glad to provide you with the
corresponding information.
Friendly,
Sven Luther
Reply to: