| 1 |
On 08/22/2009 06:40 AM, Jeremy Olexa wrote: |
| 2 |
> Nikos Chantziaras wrote: |
| 3 |
>> On 08/22/2009 05:59 AM, Nikos Chantziaras wrote: |
| 4 |
>>> On 08/22/2009 05:39 AM, Sebastian Pipping wrote: |
| 5 |
>>>> Sebastian Pipping wrote: |
| 6 |
>>>>> Commits are done automatically, triggering and pushing is |
| 7 |
>>>>> manual at the moment. |
| 8 |
>>>> |
| 9 |
>>>> By now a cron-based setup is running syncing the pure-funtoo overlay |
| 10 |
>>>> (and therefore also its atom and rss feeds) every 24 hours. |
| 11 |
>>> |
| 12 |
>>> There seems to be a bit of (minimal) duplication between pure-funtoo and |
| 13 |
>>> sunrise. |
| 14 |
>> |
| 15 |
>> Uhm, I just discovered that there are conflicts with portage too. That |
| 16 |
>> is not good. After I added pure-funtoo, it messed up my emerge -u |
| 17 |
>> world (stuff like wanting to upgrade to sys-apps/baselayout-2.1.5). |
| 18 |
>> |
| 19 |
>> pure-funtoo should not offer packages available in portage (sunrise is |
| 20 |
>> the lesser evil). |
| 21 |
> |
| 22 |
> Huh? This is true of all overlays. |
| 23 |
|
| 24 |
Not the ones I'm using. |
| 25 |
|
| 26 |
|
| 27 |
> If my overlay had baselayout-5.0 in |
| 28 |
> it, you would be upgrading to that version if you had my overlay... By |
| 29 |
> nature of overlays themselves, you should know what you are doing and |
| 30 |
> how to handle it (ie. mask >=sys-apps/baselayout-2.0.1) |
| 31 |
|
| 32 |
I use overlays for packages I can't get through portage. If they |
| 33 |
conflict, I don't use them. Masking is no solution. If I mask |
| 34 |
">=sys-apps/baselayout-2.0.1", I mask it for good, not only in the |
| 35 |
specific overlay it comes from. If portage updates to it, I'll never |
| 36 |
get it. |
| 37 |
|
| 38 |
This is quite a major pain in the ass and the reason I stay far away |
| 39 |
from overlays that offer conflicting packages. |
Archives