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