Hi all,
I'm wondering if this is even feasible before I go open a
bug/enhancement request for portage for this...
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...
This works well, and has saved me some serious pain more than once, but
it can be a pain to keep up with the updates sometimes...
What would be really helpful would be if the emerge --pretend output
could show the date (and time?) that the new ebuild was made available...
ie, instead of:
myhost : Fri Apr 11, 07:45:44 : ~
# emerge -pvuDN world
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] media-libs/libpng-1.6.10:0/16 [1.6.8:0/16] USE="-apng (-neon)
-static-libs" ABI_X86="(64) (-32) (-x32)" 878 kB
Total: 1 package (1 upgrade), Size of downloads: 878 kB
myhost : Fri Apr 11, 09:08:03 : ~
#
something like:
myhost : Fri Apr 11, 07:45:44 : ~
# emerge -pvuDN world
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild U ] media-libs/libpng-1.6.10:0/16 [1.6.8:0/16, released 4/11/14 at 13:11 am]
USE="-apng (-neon) -static-libs" ABI_X86="(64) (-32) (-x32)" 878 kB
Total: 1 package (1 upgrade), Size of downloads: 878 kB
myhost : Fri Apr 11, 09:08:03 : ~
#
Of course I don't care exactly where or how the date/time is displayed,
just that it is there...
So... is this feasible (without a lot of hard work)?
Thanks,
Charles
