Date: Mon, 06 Jan 2014 09:05:50 -0500 From: Jim Ohlstein <jim@ohlste.in> To: freebsd-questions@freebsd.org Subject: Re: Using pkgng, but building some ports with custom options Message-ID: <52CAB83E.4050606@ohlste.in> In-Reply-To: <CAAdqt-BZx7vbU7Omc4U1NALwxgZdVXqvXQyTwPkWBmhp9OLqNg@mail.gmail.com> References: <CAAdqt-BZx7vbU7Omc4U1NALwxgZdVXqvXQyTwPkWBmhp9OLqNg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, On 1/6/14, 8:49 AM, John Rogers wrote: > Hello. > > I'm looking into switching to using pkgng once FreeBSD 10 is released. > I must say that I'm very impressed so far after playing around with > it, but I have run into a question that I have been unable to find the > answer to. Is it possible to use pkg install from pkg.FreeBSD.org for > most packages, use portmaster locally for some packages when I want to > use custom build options and have it all work well together? > > A typical scenario that I want to avoid is that I have a custom built > installation of port A. Then one day the package is updated to a new > version on pkg.FreeBSD.org, which overwrites my local install when I > run pkg upgrade. I think "pkg lock " is what you want. From man page for pkg(8): " lock Prevent modification or deletion of a package." So something like: # pkg lock packagename should do the trick. I'm not certain, but you may need to remove the lock in order to upgrade it from ports, or do a forced re-installation. > > I have searched for this and found lots of information but no clear answer. > > John -- Jim Ohlstein
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?52CAB83E.4050606>