| 1 |
On 04/12/2010 11:00 AM, Brian Harring wrote: |
| 2 |
> On Mon, Apr 12, 2010 at 01:30:21PM -0400, James Cloos wrote: |
| 3 |
>> A reasonable alternative would be to have a separate variable in make.conf, |
| 4 |
>> such as ECLASS_OVERLAY_DIRS, which specifies acceptable overlays for eclasses. |
| 5 |
>> |
| 6 |
>> In most cases, users would probably only have their own, local overlay there, |
| 7 |
>> and any eclasses found there should be used in preference to any in portage |
| 8 |
>> or in the overlay the ebuild came from, if applicable. |
| 9 |
>> |
| 10 |
>> Every time portage looks for an eclass, it should check there first (caching |
| 11 |
>> what it found, to save future lookups w/in that run) and just use anything |
| 12 |
>> it finds. |
| 13 |
> |
| 14 |
> repos.conf has functionality of this sort, although you'll have to |
| 15 |
> consult the man page for the exact option name... |
| 16 |
|
| 17 |
It's called eclass-overrides and it's been mentioned earlier in the |
| 18 |
thread. |
| 19 |
-- |
| 20 |
Thanks, |
| 21 |
Zac |
Archives