Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 28 Mar 2009 17:03:38 +0100
From:      Mel Flynn <>
Cc:        Barnaby Scott <>, Paul Schmehl <>, Robert Huff <>
Subject:   Software installasion (Was: Re: Wine without X)
Message-ID:  <>
In-Reply-To: <>
References:  <> <> <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
On Saturday 28 March 2009 13:06:44 Robert Huff wrote:
> Mel Flynn writes:
> >  > Can I ask one more possibly really dumb question, to which I
> >  >  can find no answer: Is there a 'conventional', or sensible
> >  >  for one reason oranother, place to download application source to?
> >
> >  Most systems I use or inherited use a variation of ~/src ~/cvs or
> >  ~/svn, where src are the tarballs + their extracted source and
> >  cvs/svn checkouts and/or exports.
> 	I have never done this, but if I were running a private ports
> tree I would be tempted to root it (if not on a separate partition)
> at "/usr/priv_ports" or something similar and have the structure
> minic /usr/ports whereever possible.  The name would then be
> semi-intuitive, and a simple change of a few environment variables
> (perhaps in the login file of an account dedicated to working on
> those ports) would be all it took to change the framework.

A private portstree (as in: uses the ports framework for compiling and 
installing software, including registering the port in /var/db/pkg) is best 
kept in /usr/ports/local. One needs to set VALID_CATEGORIES=local in 
/etc/make.conf and optionally add SUBDIR+=local in /usr/ports/Makefile.local 
if one cares about the ports ending up in the INDEX and make search.

Ideally software not registering itself inside /var/db/pkg (as in software 
compiled by hand) should NOT be installed in $LOCALBASE (/usr/local by 
default) as there is no guarantee through the ports CONFLICTS mechanism, that 
a port overwrites files installed by your hand-compiled software.


Want to link to this message? Use this URL: <>