Staging support, man pages, MANx and portlint

Lev Serebryakov lev at
Tue Jan 21 17:57:34 UTC 2014

Hello, John.
You wrote 21 января 2014 г., 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}-

>>  How could I turn on gizpping of man pages in such case? 
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.

// Black Lion AKA Lev Serebryakov <lev at>

More information about the freebsd-ports mailing list