setting up a ports infrastructure outside of /usr/ports

[Michael C. Shultz]

On Wednesday 21 April 2004 03:11 pm, Oliver Fischer wrote:
> Hello,
>
> I would like to ports some programs but before I will start, I would
> like to have a separate directory for it. So so my question is:
>
> Is it possible:
>
> 1. to have the ports directory in my home directory? I
>      think yes.
>
> 2. to build and to install a port as normal user to
>     a via PREFIX specified directory?
>
> 3. to use a different pkgdb directory than /var/db/pkg for
>     the ports build in this manner?
>
>
> Regards,
> 	Oliver Fischer
> _______________________________________________
> freebsd-ports at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-ports
> To unsubscribe, send any mail to "freebsd-ports-unsubscribe at freebsd.org"

Here is how I do it:
------------------------------------------------
Here is how to handle locally installed ports if you plan to take advantage of 
some of FreeBSD's port system features: 

########################################################################
* Makefile excerpt from /usr/ports/local/sysutils/portmanager/Makefile #
########################################################################
PORTNAME=           portmanager
PORTVERSION=        0.1.0
CATEGORIES=         local/sysutils
VALID_CATEGORIES+=  ${CATEGORIES}     # for FreeBSD to accept our
                                       				 # local category
                

 Simply add a "local" directory to /usr/ports and install your local ports 
under that directory. Where a normal FreeBSD port may be in 
"sysutils/{portname} the example above would reside in 
"local/sysutils/portmanager". 
------------------------------------------------
The port still installs in the normal /var/db/pkg directory so "make install", 
and and "make deinstall" work normally. The is a note in portupgrade (if you 
use that ) about adding /usr/ports/local to their config files so their 
program will ignore your ports. I think the note is in the config file 
somewhere.

-Mike