Date: Mon, 8 Sep 2008 09:16:35 -0500 From: Brooks Davis <brooks@freebsd.org> To: Randy Pratt <bsd-unix@embarqmail.com> Cc: Kai Otto <kais.deliverymail@googlemail.com>, Ken Smith <kensmith@cse.Buffalo.EDU>, freebsd-stable@freebsd.org, Ian Smith <smithi@nimnet.asn.au> Subject: Re: Fwd: FreeBSD 7.1 Content Message-ID: <20080908141635.GA20793@lor.one-eyed-alien.net> In-Reply-To: <20080907080624.078e7e13.bsd-unix@embarqmail.com> References: <20080905213656.BDB444500F@ptavv.es.net> <20080906141423.N439@sola.nimnet.asn.au> <1220762797.29265.43.camel@bauer.cse.buffalo.edu> <20080907080624.078e7e13.bsd-unix@embarqmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--fdj2RfSjLxBAspz7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sun, Sep 07, 2008 at 08:06:24AM -0400, Randy Pratt wrote: > The ports tree distribution tarball provided on the installation disks > is another area that needs some consideration. I suspect that many > people aren't aware of the need for "adoption": >=20 > http://myfreebsd.homeunix.net/hints_n_kinks/adoptportstree.html >=20 > Is it possible to provide/install the necessary file(s) along with > the ports tree such that cvsup/csup would be aware of the files > installed so that obsolete files can be removed when updating the ports > tree? The same situation probably exists for the source tree > and the documentation tree. Would it just be a matter of installing > the appropriate "checkouts.cvs:." files when the sources are > installed? >=20 > I've only done the adoption process one time and decided that its > easier to just csup a new trees right after booting the new system. IMO, an even better (but complementary) approach would be to have /usr/ports be a valid portsnap extraction and give users the option to bootstrap /var/db/portsnap. In general I'm finding it to be a much better approach. At this point I'm mostly using cvsup for development. I literally check out a separate ports tree on boxes I do ports development on and keep the main tree up to date with portsnap. I also use freebsd-update to manage most of my servers at work even ones with custom kernels (just let it update /usr/src and don't let it update the kernel). > Additionally, I've never seen a clear way of synchronizing a > local ports tree to that used to create the "LATEST" packages. I've > had to resort to building my own package sets for the slow boxes > on the network. I realize that this aspect diverges from the > subject of this thread but I do think some more thought should > be given to this aspect. With cvs there probably isn't a cost effective way to indicate this (though I suppose the package collections could include a file with a cvsup date string in them). -- Brooks --fdj2RfSjLxBAspz7 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iD8DBQFIxTPCXY6L6fI4GtQRAiyhAJsHXQ+HGjW7kEFEKhtaU210HiVM7QCeOtwi QSNW9knEAXWDa9yVXG6UNVY= =Cf7l -----END PGP SIGNATURE----- --fdj2RfSjLxBAspz7--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080908141635.GA20793>