| 1 |
On 04/01/2010 05:17 PM, Brian Harring wrote: |
| 2 |
> On Thu, Apr 01, 2010 at 05:14:20PM -0700, Zac Medico wrote: |
| 3 |
>> You can configure eclass override behavior via eclass-overrides in |
| 4 |
>> /etc/portage/repos.conf, as documented in `man portage`. There are a |
| 5 |
>> number of caveats to eclass-overrides, and that's why it's not the |
| 6 |
>> default behavior. For example, beware that you'll need to set |
| 7 |
>> PORTAGE_RSYNC_EXTRA_OPTS="--exclude=/metadata/cache" if your overlay |
| 8 |
>> eclasses modify any ebuild metadata (as documented in `man portage`). |
| 9 |
> |
| 10 |
> Why not add some boolean list to the repo definition controlling that, |
| 11 |
> rather then requiring people to specify the raw RSYNC option? |
| 12 |
> Something like REPO_OPTIONS='exclude-cache'? |
| 13 |
> |
| 14 |
> You can also jam some other options in there- one that might be useful |
| 15 |
> for folks is specifying the minimal sync period (sync this repo at |
| 16 |
> most once a day, or at most once an hour), etc. |
| 17 |
|
| 18 |
I think it would be preferable to extend the cache format to improve |
| 19 |
the validation mechanism, as discussed here: |
| 20 |
|
| 21 |
|
| 22 |
http://archives.gentoo.org/gentoo-dev/msg_cfa80e33ee5fa6f854120ddfb9b468b3.xml |
| 23 |
|
| 24 |
That said, I wouldn't be opposed to adding something like the |
| 25 |
REPO_OPTIONS='exclude-cache' approach that you suggest. |
| 26 |
-- |
| 27 |
Thanks, |
| 28 |
Zac |
Archives