Date: Fri, 4 Apr 2014 17:49:11 -0400 From: "illoai@gmail.com" <illoai@gmail.com> To: David Newman <dnewman@networktest.com> Cc: "freebsd-questions@freebsd.org" <freebsd-questions@freebsd.org> Subject: Re: yet another pkgng vs. ports management question Message-ID: <CAHHBGkqHP4UPEi2x34HafQMGa9ydumVCBAZHuYEkbyeTgh1_2g@mail.gmail.com> In-Reply-To: <533F265D.4080605@networktest.com> References: <533F265D.4080605@networktest.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4 April 2014 17:38, David Newman <dnewman@networktest.com> wrote: > I have recently taken over sysadmin chores for a FreeBSD 9.2 system that > runs ports installed with some combination of default and non-default > options. > > I don't know which ports have non-default options set. The person who > set up the system is not available. > > For purposes of keeping the system up-to-date, which option is best: > > - just run 'pkg update && pkg upgrade' > > - just update the ports tree and run 'portmaster -aD' > > - some combination of pkg and portmaster > > - something else > I'm not aware that you can use non-default options with a pure pkg (i.e. not built from source) system. Portmaster (which I use) would seem to be the obvious choice. Assuming you aren't building www/chromium on a pentium-iii, upgrades of your installed ports from source should rarely take more than a couple of hours. Also, portmaster can use pre-built packages: see the -P (& -PP) flags. If I'm not missing anything vital, those ports with an entry in /var/db/ports/ should be the ones to look at, as the changes to any options should be stored there. The biggest thing is to not fiddle too much with stuff until you have a better idea of what needs to keep running exactly as it is, for Lo! there be dragons. -- --
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAHHBGkqHP4UPEi2x34HafQMGa9ydumVCBAZHuYEkbyeTgh1_2g>