1 |
On Wed, 31 Aug 2005 14:42:16 +0200, Holly Bostick wrote: |
2 |
|
3 |
> But do you know the answer to Nick's question about what I said earlier? |
4 |
> In a 'conflict' between two ebuilds of the same name and version, one in |
5 |
> Portage and one in the overlay, does the choice of which one is used if |
6 |
> I emerge the relevant package rely on which one is most recent(ly |
7 |
> modified), or the location-- i.e., will the overlay ebuild always beat |
8 |
> the Portage ebuild even if the Portage build is newer (because it was |
9 |
> updated without changing the version number), or will the newer ebuild |
10 |
> always win out, whether it's in overlay or main Portage? |
11 |
|
12 |
The overlay takes priority, even if the file date in the main portage tree |
13 |
is newer. It's easy to test. copy a directory from the main tree to your |
14 |
overlay, touch the latest ebuild in the main tree and emerge -pv the |
15 |
package. You'll see that emerge picks the overlay version. |
16 |
|
17 |
I noticed this when I wrote my own ebuild for a package and then someone |
18 |
put it in portage. The first I new was when they released an r1 ebuild |
19 |
and emerge --update world picked it up. |
20 |
|
21 |
When you think about it, the very name "overlay" indicates that this is |
22 |
how it should work. |
23 |
|
24 |
|
25 |
-- |
26 |
Neil Bothwick |
27 |
|
28 |
I have had a perfectly wonderful evening, but this wasn't it. |