Zac Medico posted on Wed, 25 Apr 2012 23:26:24 -0700 as excerpted: > On 04/25/2012 11:18 PM, Duncan wrote: >> IOW, let's quit letting the perfect be the enemy of the good, and just >> get on with it, already. > > If that means settling on something that's fragile and prone to lots of > bug reports, then it's not really practical, because it wastes peoples > time (and time is our most valuable resource).
IMO it's trying to do too much with it that's the fragile bit. If all it does is the patching, but it /always/ does the patching (unlike the hit- and-miss we get now), and people know they need to use the overlay-ebuild method to do anything beyond patching, including if they need to re- invoke eautoreconf, then it should "just work". Right now we're talking about all this fancy stuff, detecting when we need to automatically run eautoreconf, etc, and /that/ seems to me to be the fragile bit. Of course that's why I have preserve-libs turned off here as well. IMO it's a too complex solution to a simple problem, and cleaning up when it breaks is worse than simply dealing with the problem using current proven technology. But at least epatch-user doesn't break the modified ebuild in overlay method, like preserved-libs breaks the normal revdep-rebuild scans so they report no packages to rebuild. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman
