Port Makefiles and the MANPREFIX macro
Kris Kennaway
kris at obsecurity.org
Thu Sep 14 23:25:15 PDT 2006
On Fri, Sep 15, 2006 at 07:22:15AM +0100, Matt Dawson wrote:
> Hi all,
> Currently doing battle with some port updates and I have come across a
> strange problem. It's probably my fault, but some guidance would be
> appreciated.
>
> Three of the ports I maintain have decided that the man pages belong in
> ${PREFIX}/share/man/man(n). Now, reading the Porter's Handbook, it appears
> this is exactly what the MAN[n]PREFIX macro is for, and sure enough after
> removing the man page from pkg-plist and telling the Makefile about it, the
> ports system compresses the resultant man page in its new location. So far so
> good.
>
> However, on deinstall, if appeand two lots of ${PREFIX} when trying to remove
> the man page. For example, grig installs a man page
> to /usr/local/share/man/man1/grig.1 (for a ${PREFIX} of /usr/local). The
> deinstall routine trys to delete grig.1.gz
> from /usr/local/share//usr/local/share/man/man1, which is just a little
> crazy. Note the two slashes between the two iterations of the MANPREFIX.
>
> Any clues, folks? I'd like to get these updates in before the ports tree is
> frozen for 6.2 if at all possible.
Don't include MANPREFIX=${PREFIX}... since it's apparently being used
as ${PREFIX}${MANPREFIX}; you could confirm this by reading
bsd.port.mk.
Kris
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20060915/7dbe1124/attachment.pgp
More information about the freebsd-ports
mailing list