Date: Thu, 12 Apr 2007 21:26:39 +0100 From: RW <fbsd06@mlists.homeunix.com> To: freebsd-ports@freebsd.org Subject: Re: Using portsnap after sysinstall Message-ID: <20070412212639.6299d37f@gumby.homeunix.com> In-Reply-To: <20070412172357.GD82155@lor.one-eyed-alien.net> References: <20070412122954.493cajcveoko88ko@mail.schnarff.com> <20070412172357.GD82155@lor.one-eyed-alien.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > 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. If your aim is to get a reliable system up quickly and easily, running portsnap can be the wrong thing to do.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070412212639.6299d37f>