Date: Tue, 21 Jan 2014 21:57:26 +0400 From: Lev Serebryakov <lev@FreeBSD.org> To: John Marino <freebsd.contact@marino.st> Cc: marino@freebsd.org, freebsd-ports@freebsd.org Subject: Re: Staging support, man pages, MANx and portlint Message-ID: <1205487257.20140121215726@serebryakov.spb.ru> In-Reply-To: <52DEB306.4040405@marino.st> References: <1328952771.20140121190647@serebryakov.spb.ru> <52DEB306.4040405@marino.st>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, John.
You wrote 21 =D1=8F=D0=BD=D0=B2=D0=B0=D1=80=D1=8F 2014 =D0=B3., 21:48:54:
JM> Why are you using a non-standard path for man pages?
JM> You can using the post-install target to move them to their expected
JM> location if the port installs them in the wrong place.
Because I try to mimic upstream package as close as possible -- and have
it in one self-contained directory, like we have OpenJDKs for example. I
try to do that because it is embedded development toolchain, end
True(tm)(r) embedded developers prefer to have one version of toolchaim,
and not different versions of binutils, gcc, libc (newlib-nano), etc. Also,
man pages are rather generic ar/ld/gcc/name-your-gnu-toolchain-tool pages,=
so
it is bad idea to install them into system mangapges, even with ${TARGET}-
prefix.
>> How could I turn on gizpping of man pages in such case?=20
JM> I know you already got your answer, but I think putting the pages in a
JM> standard location is a better solution.
I love hier(7) too, but this case is rather special.
--=20
// Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1205487257.20140121215726>