PREFIX problems...

Vasil Dimov vd at FreeBSD.org
Sun Feb 12 22:43:44 PST 2006


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Fri, Feb 10, 2006 at 08:15:07PM +0100, Anders Troback wrote:
> 
> I did this with LOCALBASE as you told me and the port installs just
> fine but now I have lots of empty folders:
> 
> /usr/local/bigsister/libdata
> /usr/local/bigsister/include
> /usr/local/bigsister/libexec
> etc.
> 
> do you know know where the are coming from and/or how I cope with them?
> 

Maybe you are looking for NO_MTREE=yes (bsd.port.mk is your friend)

By the way I discussed that issue with some people and it showed that
PREFIX?=${LOCALBASE}/bigsister has some disadvantages like that if one
types ``make PREFIX=/home/joe'' for example, then the port will not be
installed in its own bigsister/ subdirectory (as it does by default) and
/home/joe will get populated with all the bigsister stuff.

Using CONFIGURE_ARGS=--prefix=${PREFIX}/bigsister has also some
disadvantages like that if one types ``make PREFIX=/home/joe'' one
would expect executables to be placed in /home/joe/bin/ rather than
/home/joe/bigsister/bin/

You see - both methods have some disadvantages. The perfect solution
would be to patch bigsister to be hier(7) compatible - e.g. not to
install *.pm files in bin/, install documentation in ${DOCSDIR}, man
pages in ${MANPREFIX}, miscellaneous data in ${DATADIR} and
configuration stuff in ${PREFIX}/etc/ or ${PREFIX}/etc/bigsister.

Happy hacking ;-)

- -- 
Vasil Dimov
-----BEGIN PGP SIGNATURE-----

iD8DBQFD8CqdFw6SP/bBpCARAryKAJ9r9ViV1YGEwjlz7xlpQoHhs8x4LwCdGtxY
4dzD+rtyDJfBBpMir4/AvFM=
=N9Ta
-----END PGP SIGNATURE-----


More information about the freebsd-ports mailing list