Date: Tue, 22 Apr 2003 00:39:59 -0700 (PDT) From: Doug Barton <DougB@FreeBSD.org> To: Tim Aslat <tim@spyderweb.com.au> Cc: freebsd-ports <freebsd-ports@FreeBSD.org> Subject: Re: question about /usr/ports structure Message-ID: <20030422003739.Y659@znfgre.tberna.bet> In-Reply-To: <20030422095043.3d3095ec.tim@spyderweb.com.au> References: <20030422095043.3d3095ec.tim@spyderweb.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 22 Apr 2003, Tim Aslat wrote:
> Hi All,
>
> I'm wondering if someone can enlighten me on the /usr/ports directory
> structure for development. What I'm looking for is a place I can put
> ports I'm working on until they are ready for submission, without
> having them overwritten each time I cvsup my ports tree (daily cron job)
As a couple people already alluded to, you can store the ports directories
anywhere on your system. For example, ~/ports would be fine. As long as
you have all the files FOR the port in the working directory, it should
all work. The reason is that the port Makefile's include bsd.port.mk (or
pre. and post.), which means that the directory itself can be anywhere.
HTH,
Doug
--
This .signature sanitized for your protection
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030422003739.Y659>