Ok,
Well, what if instead we were to try and treat the overlay trees as
exactly that, overlays. So the moves were used from the lowest layer
(ie the main tree) unless a higher up layer overrode them, could that
work? It would mean effectively that the overlay moves were global, but
I guess you'd then end up losing updates to the main tree if a file like
4Q-2005 was overridden...
Can anyone think of a pratical solution to this problem other than
either a major rework of portage's tree handling system, or by having
the two packages block each other and relying on the user to fix the
tree up manually whenever this happens? Any ideas would be welcome,
it's a problem I'd really like to fix. Thanks very much,
Mike 5:)
--
[email protected] mailing list
