On Tue, Aug 30, 2011 at 05:59:21PM -0400, Joey Hess wrote:
> Yann Dirson wrote:
> > I tried things like:
> >
> > build-arch:
> > dh_auto_build -a
> > docbook-to-man debian/tulip.sgml > debian/tulip.1
>
> You're not running dh_auto_configure which dh would normally run here.
>
> Why not just run "dh build-arch" in the build-arch target?
Well, I am tempted to think my problems come from the manpage example
not doing that in the first place :)
Another thing that I feel lacks in the manpage is a user-level
description of what the debhelper log tries to achieve. Its details
are mentionned in "INTERNALS", which is probably not intended to be
necessary to read for an understanding of "what happenned ?". That
is, the dh manpage should probably mentions earlier that dh remembers
what dh_* commands have been run. This would allow to explain that
one can run things like the following without package-specific actions
being overridden with general ones:
override_dh_foo:
dh_foo -ppblurb
whatever
dh_foo
OTOH I got surprised (although I think I understand what happenned
behind the scenes) that running build-arch runs auto_configure only
"for arch packages", whereas it is for most packages a generic thing,
so that running build-indep afterwards cause cmake to be run again. I
guess this can cause unwanted rebuilds when one then runs build-arch
again.
Best regards,
--
Yann
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
