Date: Sun, 15 Aug 2021 16:28:18 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: LuMiWa <lumiwa@dismail.de> Cc: Mike Clarke <jmc-freebsd2@milibyte.co.uk>, FreeBSD Questions <freebsd-questions@freebsd.org> Subject: Re: pkg lock Message-ID: <CAN6yY1tF=qKFs7F7ZFHnFUjzRMyQp=hoT4m0RjGM2qrLCMLVtg@mail.gmail.com> In-Reply-To: <20210814081410.0e6e2a12@dismail.de> References: <20210812125424.47ab3bb9@dismail.de> <5562216.8T7jmnknE8@curlew> <20210814081410.0e6e2a12@dismail.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Aug 14, 2021 at 5:14 AM LuMiWa via freebsd-questions < freebsd-questions@freebsd.org> wrote: > On Sat, 14 Aug 2021 11:14:52 +0100 > Mike Clarke <jmc-freebsd2@milibyte.co.uk> wrote: > > > On Thursday, 12 August 2021 17:54:24 BST LuMiWa via freebsd- > > questions wrote: > > > > > I am using binary packages (latest) on FreeBSD 13.0-RELEASE. > > > I have 8 applications where I have my own settings. Is it correct > > when > > > I built the and install that I should use "pkg lock name" of > > > port/package, please? Or is something other. > > > > Yes, that's the way to go but if you rebuild the port for any reason > > you will need to unlock it for the duration of the build otherwise > > the final stage of installing the package will fail. > > > > Thank you, I did and I wrote which ports I locked :). > If you build ports with portmaster, it will report the locked port if it attempts to rebuild it and ask if you want to update anyway. If you reply 'Y', it will unlock the port, rebuild and install it and re-lock the port. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1tF=qKFs7F7ZFHnFUjzRMyQp=hoT4m0RjGM2qrLCMLVtg>