Date: Mon, 21 Apr 2003 17:27:17 -0700 From: Adam Weinberger <adamw@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: <20030422002717.GZ25227@vectors.cx> 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
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >> (04.21.2003 @ 1720 PST): Tim Aslat said, in 1.2K: << > 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? >> end of "question about /usr/ports structure" from Tim Aslat << That's one massive .sig you've got there, Tim ;;) cvsup won't hose anything you have set up outside of the normal cvsup tree. /usr/ports/anything will be left alone by cvsup. # Adam - -- Adam Weinberger vectors.cx >> adam@vectors.cx FreeBSD.org << adamw@FreeBSD.ORG #vim:set ts=8: 8-char tabs prevent tooth decay. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (FreeBSD) iD8DBQE+pIxlo8KM2ULHQ/0RAoxaAJ9B4qVKf4zzeWspkP3PPyfzafSHUACg0Bwf L2wAUPVknO1njyrk1HgIs6g= =5ljH -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030422002717.GZ25227>