Neil Bothwick schreef: > On Wed, 31 Aug 2005 14:42:16 +0200, Holly Bostick wrote: > > >> But do you know the answer to Nick's question about what I said >> earlier? In a 'conflict' between two ebuilds of the same name and >> version, one in Portage and one in the overlay, does the choice of >> which one is used if I emerge the relevant package rely on which >> one is most recent(ly modified), or the location-- i.e., will the >> overlay ebuild always beat the Portage ebuild even if the Portage >> build is newer (because it was updated without changing the version >> number), or will the newer ebuild always win out, whether it's in >> overlay or main Portage? > > > The overlay takes priority, even if the file date in the main portage > tree is newer.
OK, now that I'm thinking about it more (given that I'm actually awake now), I do remember that I had to remove my overlay build of taskjuggler in order to emerge the one that had been included in Portage. So I was mistaken. It can happen, sorry ;) . Which is why, of course, I asked you, Neil (because you know, like, everything, just about :D ). > It's easy to test. copy a directory from the main tree to your > overlay, touch the latest ebuild in the main tree and emerge -pv the > package. You'll see that emerge picks the overlay version. You should know better than using the phrase 'it's easy' and the command "'touch' whatever" in the same sentence when you're talking to me :) . I kinda know how to 'touch', and I just learned how to 'grep' simple strings (the operative word being 'simple'). It *is* easy, but honestly, I'm well known to be the village idiot when it comes to the CLI, so your easy test doesn't come naturally to me at all. :P But it's good to be reminded of how such things can quickly be done. Repeat it often enough, and it might even get caught in the sieve that can be my brain. > > I noticed this when I wrote my own ebuild for a package and then > someone put it in portage. The first I new was when they released an > r1 ebuild and emerge --update world picked it up. Yes, I think that's what happened to me with taskjuggler as well. > > When you think about it, the very name "overlay" indicates that this > is how it should work. I suppose there's no way to avoid there being *some* issue-- this way, you have to actively watch Portage to see if today is perhaps the happy day that your overlay build is obsoleted; the other way, Portage would be obsoleting your overlay build arbitrarily. I don't see either of these as optimal conditions (since the goal, imo, is to be using Portage builds and as few overlay builds as possible, and neither of these conditions gives you a painless way to Return To Portage, as it were), but I agree that the way it's currently done is the better of two sub-optimal choices. Holly -- gentoo-user@gentoo.org mailing list
