Date: Mon, 30 Mar 2015 07:11:34 -0700 From: "Chris H" <bsd-lists@bsdforge.com> To: <freebsd-ports@freebsd.org> Subject: Re: USES vs BUILD_DEPENDS Message-ID: <e4c2b85068fcd7b0f23788b2a45eb968@ultimatedns.net> In-Reply-To: <Pine.GSO.4.64.1503300843030.18384@sea.ntplx.net> References: <Pine.GSO.4.64.1503291236300.14490@sea.ntplx.net> <20150329165301.GA91058@ivaldir.etoilebsd.net> <Pine.GSO.4.64.1503291311320.14789@sea.ntplx.net>, <Pine.GSO.4.64.1503300843030.18384@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 30 Mar 2015 08:50:44 -0400 (EDT) Daniel Eischen <deischen@freebsd.org> wrote > On Sun, 29 Mar 2015, Daniel Eischen wrote: > > > On Sun, 29 Mar 2015, Baptiste Daroussin wrote: > > > >> On Sun, Mar 29, 2015 at 12:41:21PM -0400, Daniel Eischen wrote: > >>> I have a port which needs pod2man just to build the man file > >>> during installation. Why do I need USES= pod2man:perl5 just to > >>> build the port? It doesn't seem feasible to use BUILD_DEPENDS > >>> because there is no generic perl5 port. > >>> > >> Have you tried using pod2mdoc ? > > > > No, I didn't know about it, I will check it out. I searched other > > ports (grep) and found pod2man used. My port's (internal) > > doc/Makefile uses pod2man. > > pod2mdoc doesn't seem compatible with the way pod2man is used: > > pod2man --release="'cat .version'" --center="Foo" $*.pod > > in particular, the -r or --release option. Are you able to generate the man page on your own machine? Point being; you could simply pass a CONFIGURE_ARGS line that disables/turns off the option to create the man page, and put the man page you've created locally into files/, and add it to post-install: Just a thought. --Chris > > -- > DE > _______________________________________________ > freebsd-ports@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-ports > To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e4c2b85068fcd7b0f23788b2a45eb968>