Hi all, I believe many developers like to create and scan ebuilds that live in their overlays before moving into their CVS checkout and committing. Up until portage-2.0.51-r15 this was possible, but there was also a problem that overlays were used when checking for issues within the CVS checkout. Due to this, overlays were completely disabled in -r15.
The patch[1] should allow for both. There was a bit of chopping and changing of sections of code though, so please confirm that I haven't forgotten about a used variable somewhere that results in some traceback. The logic essentially goes: 1. Are we in an overlay? 2. If yes, then record the overlay. 3. Otherwise, are we in PORTDIR? 4. If yes, then record it. 5. Otherwise, can a profiles/ dir be found? 6. If yes, then record it. 7. Otherwise, fail. 8. Does our recorded dir have a profiles/ dir? 9. If yes, then set PORTDIR to it and unset PORTDIR_OVERLAY 10. Otherwise, set PORTDIR_OVERLAY to it and keep PORTDIR Let me know if you find any issues. Regards, Jason Stubbs [1] http://dev.gentoo.org/~jstubbs/patches/2.0.51-r15/repoman-overlay-scanning.patch P.S. Thanks to solar for pointing out bugs before this email went out :) -- [email protected] mailing list
