Date: Wed, 2 Jul 2014 22:54:39 -0600 (MDT) From: Warren Block <wblock@wonkity.com> To: Matthew Pherigo <hybrid120@gmail.com> Cc: freebsd-questions <freebsd-questions@freebsd.org>, Chris Stankevitz <chrisstankevitz@gmail.com> Subject: Re: Updating the ports collection that came with the OS Message-ID: <alpine.BSF.2.11.1407022252100.95941@wonkity.com> In-Reply-To: <D389D5E5-C24B-4729-8704-21D7ED7C56C2@gmail.com> References: <CAPi0pstB62CqQ-9SQ54UTunUUNmVMwC5R9irzeRidX9-oVg-wA@mail.gmail.com> <D389D5E5-C24B-4729-8704-21D7ED7C56C2@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 2 Jul 2014, Matthew Pherigo wrote: > Chris, > > Both methods work fine for ports collections installed along with the OS. Just running "portsnap fetch update" will your the ports directory. For the Subversion method, our docs recommend removing /usr/ports before checking out the working copy. Otherwise there are likely to be old files in there that are not managed by Subversion. I don't think that is a problem with portsnap. Don't know how bsdinstall installs a ports tree, either, it might just untar an archive.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.11.1407022252100.95941>