On 4/11/2014 4:37 PM, Neil Bothwick <n...@digimed.co.uk> wrote:
On Fri, 11 Apr 2014 09:30:43 -0400, Tanstaafl wrote:
One of the things I do to minimize getting bit by newly released buggy
ebuilds is to wait a few days after a new update is available before
updating...
Isn't that what the stable tree is for?
As I said, this has saved me some pain even on the stable tree...
You could write a script that runs emerge -ublah @world, parses the
output and then checks the timestamps of the ebuilds. It could then
filter packages based on the age of the ebuild, instead of showing a date
and letting you do the work.
This is all fine and good, but not what I asked.
First, ianap, and don't have the skills to do that, and
Second, I personally would like to see this important (imho) information
right there in the emerge --pretend output, and believe that lots of
people would find it valuable.
Last - I merely asked if this was *feasible*. Ie, it seems to me like
the relevant information is already available, portage just needs to
make use of it.
I'd even be fine with it only being made a part of the verbose output,
since I always do 'emerge -pvuDN world' anyway...
