Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 2 Sep 2004 17:59:41 +0200
From:      Oliver Eikemeier <eikemeier@fillmore-labs.com>
To:        Mike Patterson <mike.patterson@unb.ca>
Cc:        freebsd-ports@freebsd.org
Subject:   Re: PREFIX "cleverness"
Message-ID:  <19DD9455-FCF9-11D8-B720-00039312D914@fillmore-labs.com>
In-Reply-To: <41372013.2070203@unb.ca>

next in thread | previous in thread | raw e-mail | index | archive | help
Mike Patterson wrote:

> I use quotation marks because I'm not certain what I intend to do is
> clever, really, but it would make my life a lot easier.
>
> I'm trying to make ports install themselves to something like
> PREFIX/portname/, so that libtool15's binary would be
> PREFIX/libtool15/bin and its man pages would be PREFIX/libtool15/man,
> etc.

make PREFIX='/usr/local/${PORTNAME}' install

... although it seems to be smarter to use LATEST_LINK instead of the 
ports name.

> A quick read through the handbook and bsd.ports.mk imply that there's no
> current way to do it, but perhaps I missed something.  I'd be willing to
> try hacking up Mk bits (either for committing or just for myself).

You need to build a link farm from LOCALBASE to the files installed by 
your port, since other ports expect them to be there.  Another 
consequence is that new CONFLICTS checking routines are required.

> Or am I insane for wanting to force ports infrastructure to conform to
> this sort of localism?

Your degree of insanity depends on just what you are trying to 
accomplish. If you want to do this `just because it can be done' -  yes. 
If you believe it will better separate the packing lists of ports - 
maybe. If you attempt to pkgsrcify the FreeBSD ports collection - who 
knows.
-Oliver



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19DD9455-FCF9-11D8-B720-00039312D914>