| 1 |
On 13/02/15 22:16, Andrew Savchenko wrote: |
| 2 |
> On Fri, 13 Feb 2015 20:29:07 +0200 Nikos Chantziaras wrote: |
| 3 |
>> I migrated my portage config to the new repos.conf system. I now have a |
| 4 |
>> file /etc/portage/repos.conf/local.conf: |
| 5 |
>> |
| 6 |
>> [Local] |
| 7 |
>> location = /usr/local/portage |
| 8 |
>> auto-sync = no |
| 9 |
> |
| 10 |
>> And removed the path from make.conf. |
| 11 |
>> |
| 12 |
>> However, now layman overlays override my local repo. If I copy an ebuild |
| 13 |
>> to /usr/local/portage (for modifications) and try to emerge it, it is |
| 14 |
>> not emerged. Instead, the ebuild from the other overlay is emerged. |
| 15 |
>> |
| 16 |
>> How do I make my local overlay have the highest priority so that it |
| 17 |
>> overrides *everything*? |
| 18 |
> |
| 19 |
> Try to add |
| 20 |
> priority = 100 |
| 21 |
> to local.conf |
| 22 |
|
| 23 |
Thanks! That works. To be sure, I used 99999999. |
| 24 |
|
| 25 |
On a side note, someone should inform the portage devs that higher |
| 26 |
priorities should equal lower numbers. Don't do it the opposite way to |
| 27 |
the rest of the world, please :-P |
Archives