On Sat, 12 Apr 2014 13:44:30 -0400
Tanstaafl wrote:
> Last - I merely asked if this was *feasible*.
It was unclear to me whether this is in the context of it being
feasible for (other) users, or whether this is in the context of making
it work in Portage; I've not replied earlier because I thoug
On 4/11/2014 4:37 PM, Neil Bothwick 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
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?
> This works well, and has saved me some s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 04/11/14 17:30, Tanstaafl wrote:
> 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...
I thought of something like this, but in emerge --search summary
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
5 matches
Mail list logo
