On Thursday 21 September 2006 11:08, Brian Harring wrote: > On Thu, Sep 21, 2006 at 10:43:11AM -0400, Mike Frysinger wrote: > > i'm referring to the specific file of course, not anything else in the > > package ... so integrating the hack eutils.eclass:preserve_old_lib() into > > portage so it isnt a hack (not a knock against the current implementation > > here; it's always going to be a hack until portage manages proper > > unmerging of the ABI library) > > The reason folks aren't talking about using NEEDED is that NEEDED data > is generated _after_ building;
as well it should be ... trying to enumerate the linking ABI possibilities before hand is not doable and not worth wasting the time of maintainers when it can be automated > getting the info into the resolver > up front allows for a helluva lot more options, and makes stuff like > ensuring you have all sources required downloaded *prior* actually > simple to do, rather then inserting recalculating hacks into the > resolver. rather than integrating it all into the resolver in a one-pass system, a two pass system would work: - build all the packages requested - after each package, if an ABI library is being removed, check to see if it is needed by any other package. if it is needed, record it and preserve it and move on - once all the packages requested have been merged, you start the second phase and calculate everything that needs to be rebuilt. as ABI libs are no longer needed on a system, portage can scrub them out -mike
pgprFrngNUjNQ.pgp
Description: PGP signature
