On 03/31/12 17:52, Ciaran McCreesh wrote: > On Sat, 31 Mar 2012 12:44:03 +0300 > Alex Alexander <alex.alexan...@gmail.com> wrote: >> @preserved-libs works very well and is awesome. hack or not. IMO it >> should be in stable already. I've been using it on stable production >> boxes for years without any issues :) > > ...and here we see the problem. You think that "I haven't noticed it > break" means "it works". > > The problem with preserved-libs (and emerge --jobs, for that matter) is > that the design is "I can think of a few ways where it might break, so > I'll hard-code in special cases to handle those, but in general I > can't think of what other problems there are so it's fine". That's a > bad way of doing things. > Good enough is the worst enemy of perfect.
While we have s 98% solution that doesn't handle all corner cases you have a theoretical construct in your brain that might in theory cover 100% of all cases, but it's in your brain where I can't use it, so ... I'll take the pragmatic approach and use what works.
