| 1 |
On 04/01/2010 04:41 PM, James Cloos wrote: |
| 2 |
> And given that portage inappropriately ignores a fixed eclass in the |
| 3 |
> OVERlay, that means that every time one syncs one must re-patch the |
| 4 |
> offending eclasses. |
| 5 |
|
| 6 |
You can configure eclass override behavior via eclass-overrides in |
| 7 |
/etc/portage/repos.conf, as documented in `man portage`. There are a |
| 8 |
number of caveats to eclass-overrides, and that's why it's not the |
| 9 |
default behavior. For example, beware that you'll need to set |
| 10 |
PORTAGE_RSYNC_EXTRA_OPTS="--exclude=/metadata/cache" if your overlay |
| 11 |
eclasses modify any ebuild metadata (as documented in `man portage`). |
| 12 |
-- |
| 13 |
Thanks, |
| 14 |
Zac |
Archives