1 |
Hi all, |
2 |
|
3 |
I'm wondering if this is even feasible before I go open a |
4 |
bug/enhancement request for portage for this... |
5 |
|
6 |
One of the things I do to minimize getting bit by newly released buggy |
7 |
ebuilds is to wait a few days after a new update is available before |
8 |
updating... |
9 |
|
10 |
This works well, and has saved me some serious pain more than once, but |
11 |
it can be a pain to keep up with the updates sometimes... |
12 |
|
13 |
What would be really helpful would be if the emerge --pretend output |
14 |
could show the date (and time?) that the new ebuild was made available... |
15 |
|
16 |
ie, instead of: |
17 |
|
18 |
> myhost : Fri Apr 11, 07:45:44 : ~ |
19 |
> # emerge -pvuDN world |
20 |
> |
21 |
> These are the packages that would be merged, in order: |
22 |
> |
23 |
> Calculating dependencies... done! |
24 |
> [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 |
25 |
> |
26 |
> Total: 1 package (1 upgrade), Size of downloads: 878 kB |
27 |
> myhost : Fri Apr 11, 09:08:03 : ~ |
28 |
> # |
29 |
|
30 |
something like: |
31 |
|
32 |
> myhost : Fri Apr 11, 07:45:44 : ~ |
33 |
> # emerge -pvuDN world |
34 |
> |
35 |
> These are the packages that would be merged, in order: |
36 |
> |
37 |
> Calculating dependencies... done! |
38 |
> [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 |
39 |
> |
40 |
> Total: 1 package (1 upgrade), Size of downloads: 878 kB |
41 |
> myhost : Fri Apr 11, 09:08:03 : ~ |
42 |
> # |
43 |
|
44 |
Of course I don't care exactly where or how the date/time is displayed, |
45 |
just that it is there... |
46 |
|
47 |
So... is this feasible (without a lot of hard work)? |
48 |
|
49 |
Thanks, |
50 |
|
51 |
Charles |