> Why not reverse the two commands:
> override_dh_installman:
> /somepath/create-a-man-page > debian/packagename.1
> dh_installman --
> Let dh_installman install the generated manpage.
To my mind this violates modularity, in that *building* the man page
is happening during what
Ole Wolf writes:
> I am building a package where I'm overriding the man page generation to
> include man pages that are generated at build time. A simplified version
> of the override in my debian/rules is:
>
> override_dh_installman:
> dh_installman --
> /somepath/create-a-man-page > ${m
On Fri, 01 Jun 2012 23:37:16 +0200, Ole Wolf wrote:
> > PACKAGE = $(shell dh_listpackages)
> > TMP = $(CURDIR)/debian/$(PACKAGE)
> > Using this method, you can substitute $(PACKAGE) for the package name,
> > which may make your rules file a little prettier...
> Thanks! It turns out I wasn't en
Jonathan,
fre, 01 06 2012 kl. 15:36 -0400, skrev Jonathan Yu:
> This may only be a partial help for you (you will still need to
> specify the /usr/... etc stuff), but this is the method we use in the
> Debian Perl group to build the path:
> PACKAGE = $(shell dh_listpackages)
> TMP = $(CURDIR)/
Hi,
On Fri, Jun 1, 2012 at 12:33 PM, Ole Wolf wrote:
> However, I don't know how to specify the target path for the man pages,
> which I've tentatively indicated by ${mandir} in the above snippet. I'm
> not using autoconf, which seems to set some path variables.
>
This may only be a partial hel
5 matches
Mail list logo
