portlint: DATADIR and NOEXAMPLEDOCS

Stephen Montgomery-Smith stephen at missouri.edu
Wed Jul 20 20:40:47 UTC 2011


I have a couple of questions.

1)  Why does portlint complain if a port is not DATADIR compliant?

What was the rationale behind making ports DATADIR compliant, so that if 
one types "make install DATADIR=/somewhere_else" then what would be 
stored in /usr/local/share/port_name will now be in /somewhere_else.

If there are one hundred ports depending upon port x/y, and those ports 
use the x/y DATADIR, then each of those hundred ports will have to include:
DATADIR!=	cd ${.CURDIR}/../../x/y && make -V DATADIR

This will really slow down makeindex.

It seems to me that you cannot use:
DATADIR=	`cd ${.CURDIR}/../../x/y && make -V DATADIR`
because this won't properly set PLIST_SUB.

2)  Why does portlint NOT complain if a port is not NOPORTEXAMPLES 
compliant?

This would seem a natural extension of portlint complaining if a port is 
not NOPORTDOCS compliant.

Stephen


More information about the freebsd-ports mailing list