Re: pkg 1.4 freeze please test test test!

--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkoberman_at_gmail.comOn Mon, Nov 3, 2014 at 5:09 PM, Henry Hu <
henry.hu.sh_at_gmail.com> wrote:

> On Mon, Nov 3, 2014 at 4:48 PM, Freddie Cash <fjwcash_at_gmail.com> wrote:
>
> > On Mon, Nov 3, 2014 at 1:40 PM, Hans Petter Selasky <hps_at_selasky.org>
> > wrote:
> >
> > > Is it possible when upgrading a system via "pkg" to selectivly switch
> > > upgrades ON/OFF. For example I have a custom ffmpeg install and would
> > like
> > > to keep it every time I do a binary upgrade?
> > >
> >
> >
> > ​# man pkg-lock
> >
> > ;)
> >
> > I believe that's what you are looking for.​  No idea how well it works
> > long-term, though, or if you lock a large number of packages.
> >
>
> I also use pkg-lock, but it has several problems:
> * You may miss updates. They are skipped during pkg upgrade
> * "xxx is locked and may not be modified" is displayed every time you do
> something like pkg upgrade. If you have multiple pkgs locked, it may be
> annoying.
>
> It would be easier to update the pkgs by having something like portmaster
> -P.
> --
> Cheers,
> Henry


I simply do periodic(8) weekly runs of "pkg version -vRl\<" to catch any
port that has not been updated due to being locked. On option to only
report locked packages would simplify this and looks to me like it would be
pretty easy to add, but unless you have a lot of locked packages, it's not
a problem.
--
R. Kevin Oberman, Network Engineer, Retired
E-mail: rkoberman_at_gmail.com