Date: Thu, 12 Apr 2007 15:45:03 -0500 From: Brooks Davis <brooks@freebsd.org> To: RW <fbsd06@mlists.homeunix.com> Cc: freebsd-ports@freebsd.org Subject: Re: Using portsnap after sysinstall Message-ID: <20070412204503.GA85046@lor.one-eyed-alien.net> In-Reply-To: <20070412212639.6299d37f@gumby.homeunix.com> References: <20070412122954.493cajcveoko88ko@mail.schnarff.com> <20070412172357.GD82155@lor.one-eyed-alien.net> <20070412212639.6299d37f@gumby.homeunix.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--9amGYk9869ThD9tj Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Apr 12, 2007 at 09:26:39PM +0100, RW wrote: > On Thu, 12 Apr 2007 12:23:57 -0500 > Brooks Davis <brooks@freebsd.org> wrote: > > > > I really wish sysinstall would install a copy of ports created by > > portsnap and provide an option to install the associated working > > files. As things stand, I never install the ports collection from > > sysinstall because it takes forever and I just end up deleting it. >=20 > IMO the current behaviour is actually very sensible. The ports tree on > the disk is from a period of time when maintainers were holding-off > doing anything radical, and just fixing bugs - it's the closest thing > we have to a ports release. It's also the same snapshot that was used > to create the binary packages, which minimizes dependency problems if > you need to mix ports and packages. >=20 > If your aim is to get a reliable system up quickly and easily, running > portsnap can be the wrong thing to do. I've apparently been unclear about what I'm suggesting. You are correct that actually running portsnap as part of sysinstall would be unexpected. That is not what I'm suggesting. What I am suggesting is that the ports tarball on the release CD be replaced with two new ones containing a tarball of the ports tree as created by "make release" running "portsnap fetch && portsnap extract" and a tarball of /var/db/portsnap. This would result in a system where the admin could choose to use the ports as shipped or could immediatly type "portsnap fetch && portsnap update" to get the latest version without having to do the giant initial download. Actually, a better idea would be to ship only a custom copy of /var/db/portsnap corresponding to the tagged ports tree and create the ports tree from it in sysinstall. -- Brooks --9amGYk9869ThD9tj Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (FreeBSD) iD8DBQFGHppOXY6L6fI4GtQRAgx9AKCKd2/JanI4nEN3pNYapFN/Qtt7bACfSHF7 qBrKlzQL7HwCJzZ79EjQkS4= =mwhJ -----END PGP SIGNATURE----- --9amGYk9869ThD9tj--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070412204503.GA85046>