Date: Mon, 21 Apr 2003 19:10:13 -0600 (CST) From: Ryan Thompson <ryan@sasknow.com> To: Tim Aslat <tim@spyderweb.com.au> Cc: freebsd-ports <freebsd-ports@freebsd.org> Subject: Re: question about /usr/ports structure Message-ID: <20030421190655.R71670-100000@ren.sasknow.com> In-Reply-To: <20030422095043.3d3095ec.tim@spyderweb.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
Tim Aslat wrote to freebsd-ports: > 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) > > Setting aside something like /usr/ports/local would be nice, or is > there a better option? You can build a port (almost) anywhere. I routinely build experimental ports off of my home directory, for instance. - Ryan -- Ryan Thompson <ryan@sasknow.com> SaskNow Technologies - http://www.sasknow.com 901-1st Avenue North - Saskatoon, SK - S7K 1Y4 Tel: 306-664-3600 Fax: 306-244-7037 Saskatoon Toll-Free: 877-727-5669 (877-SASKNOW) North America
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030421190655.R71670-100000>