| 1 |
A reasonable alternative would be to have a separate variable in make.conf, |
| 2 |
such as ECLASS_OVERLAY_DIRS, which specifies acceptable overlays for eclasses. |
| 3 |
|
| 4 |
In most cases, users would probably only have their own, local overlay there, |
| 5 |
and any eclasses found there should be used in preference to any in portage |
| 6 |
or in the overlay the ebuild came from, if applicable. |
| 7 |
|
| 8 |
Every time portage looks for an eclass, it should check there first (caching |
| 9 |
what it found, to save future lookups w/in that run) and just use anything |
| 10 |
it finds. |
| 11 |
|
| 12 |
-JimC |
| 13 |
-- |
| 14 |
James Cloos <cloos@×××××××.com> OpenPGP: 1024D/ED7DAEA6 |
Archives