Nikos Chantziaras <realnc <at> gmail.com> writes:
> I migrated my portage config to the new repos.conf system. "repos.conf system" is very cool; thanks for posting about it; but it's brand new to me, so I cannot really give you advise. I did find this, in case you had not seen it yet: http://wiki.gentoo.org/wiki/Project:Portage/Sync I have a "mess" with different semantics for code evaluations, enhancements and ebuild hacking. I need a new semantic. I'm not going to hijack your thread, but I am going to follow this thread very closely and then attempt to clean up the myriads of old (hack) school methodologies that I have been using. Does this system effect "epatch user", as in where the patches are placed? allowing several different epatch_users codes to be in existance and tested against one another? Is the devmanual up to date on this new system? Any and all resources related to repos.conf would be of interests to post to this thread. > I now have a > file /etc/portage/repos.conf/local.conf: > [Local] > location = /usr/local/portage > auto-sync = no > And removed the path from make.conf. > However, now layman overlays override my local repo. If I copy an ebuild > to /usr/local/portage (for modifications) and try to emerge it, it is > not emerged. Instead, the ebuild from the other overlay is emerged. > How do I make my local overlay have the highest priority so that it > overrides *everything*? What version of portage are you running? 2.2.17 or 2.2.9999? What versions of python are set as your priority (default)? James
