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. 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. 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. When you think about it, the very name "overlay" indicates that this is how it should work. -- Neil Bothwick I have had a perfectly wonderful evening, but this wasn't it.
pgpj8srpnXHJb.pgp
Description: PGP signature
