Date: Mon, 9 Sep 2019 16:56:53 +0100 From: Steve O'Hara-Smith <steve@sohara.org> To: "@lbutlr" <kremels@kreme.com> Cc: freebsd-questions@freebsd.org Subject: Re: pkg lock Message-ID: <20190909165653.4806f5643d6b46cc8ee21550@sohara.org> In-Reply-To: <7C016F5C-FEA9-4EF0-9F5C-D0838A6CD2FF@kreme.com> References: <7C016F5C-FEA9-4EF0-9F5C-D0838A6CD2FF@kreme.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 9 Sep 2019 09:21:13 -0600 "@lbutlr" <kremels@kreme.com> wrote: > Before I go off on a wild tear, a couple of quick questions. > > If I want to prevent pkg update from overwriting a package I built from > ports, I need to issue a pkg lock <port> first, then if I want to rebuild > it with postmaster I pkg unlock <port>, rebuild/update the port, and then > lock the port again, yes? Yes to all of that. It is perhaps worth mentioning the benefits of make missing to get a list of dependencies before compiling a port so that you can minimise what gets compiled by installing the dependencies first (make missing | xargs pkg install -A) or thereabouts. > And there is no one-step way to say via flags or something, unlock, > rebuild, then lock at once? You could write a script :) It would be a nice addition to ports make. > Also, is there anyway to tell what has been installed via ports and what > has been installed via pkg? Or better, what has been installed with > custom options that differ from the pkg versions? I rely on 'that which is locked came from ports'. -- Steve O'Hara-Smith <steve@sohara.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20190909165653.4806f5643d6b46cc8ee21550>