Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 03 Nov 2014 22:51:05 -0800
From:      Darren Pilgrim <list_freebsd@bluerosetech.com>
To:        Kevin Oberman <rkoberman@gmail.com>
Cc:        "current@freebsd.org" <current@freebsd.org>
Subject:   Re: pkg 1.4 freeze please test test test!
Message-ID:  <54587759.4050206@bluerosetech.com>
In-Reply-To: <CAN6yY1sSB7dSbmiPy-JY1tFh7RTiV83HewXzHzZiSX1xzW9Y2Q@mail.gmail.com>
References:  <20141028231933.GG26796@ivaldir.etoilebsd.net> <20141101161332.b9c8fc19bf9fc54f73bc5c00@gmail.com> <20141101224549.GG15967@ivaldir.etoilebsd.net> <20141102102455.30d42f85ff81e079788eae06@gmail.com> <5457F64F.6090408@selasky.org> <CAOjFWZ4hEb%2B83A5vypXMM50y7Z8tunLOE6wgcwrqzY1AV1WLww@mail.gmail.com> <CAEJt7hZUAogrpN7pzQXv%2B=Ay3xx%2ByA%2Bs2-EZSbOuDR%2BXQA-90g@mail.gmail.com> <CAN6yY1sSB7dSbmiPy-JY1tFh7RTiV83HewXzHzZiSX1xzW9Y2Q@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 11/3/2014 9:50 PM, Kevin Oberman wrote:
> 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.

I just do `pkg info -ka | egrep 'yes$'`.





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54587759.4050206>