From: Brian Harring <ferringb@gmail.com>
To: gentoo-dev@lists.gentoo.org
Cc: zmedico@gentoo.org
Subject: Re: [gentoo-dev] perl eclass review - EAPI=3 + new helper eclass
Date: Thu, 1 Apr 2010 17:17:31 -0700 [thread overview]
Message-ID: <20100402001731.GO11663@hrair> (raw)
In-Reply-To: <4BB536DC.8090405@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 874 bytes --]
On Thu, Apr 01, 2010 at 05:14:20PM -0700, Zac Medico wrote:
> You can configure eclass override behavior via eclass-overrides in
> /etc/portage/repos.conf, as documented in `man portage`. There are a
> number of caveats to eclass-overrides, and that's why it's not the
> default behavior. For example, beware that you'll need to set
> PORTAGE_RSYNC_EXTRA_OPTS="--exclude=/metadata/cache" if your overlay
> eclasses modify any ebuild metadata (as documented in `man portage`).
Why not add some boolean list to the repo definition controlling that,
rather then requiring people to specify the raw RSYNC option?
Something like REPO_OPTIONS='exclude-cache'?
You can also jam some other options in there- one that might be useful
for folks is specifying the minimal sync period (sync this repo at
most once a day, or at most once an hour), etc.
~harring
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-04-02 0:19 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 11:11 [gentoo-dev] perl eclass review - EAPI=3 + new helper eclass Torsten Veller
2010-03-30 15:48 ` Alec Warner
2010-04-03 10:33 ` [gentoo-dev] " Torsten Veller
2010-04-01 23:41 ` [gentoo-dev] " James Cloos
2010-04-02 0:12 ` [gentoo-dev] " Jonathan Callen
2010-04-02 0:14 ` [gentoo-dev] " Zac Medico
2010-04-02 0:17 ` Brian Harring [this message]
2010-04-02 0:25 ` Zac Medico
2010-04-06 14:22 ` James Cloos
2010-04-06 18:39 ` Zac Medico
2010-04-12 17:17 ` James Cloos
2010-04-12 17:30 ` James Cloos
2010-04-12 18:00 ` Brian Harring
2010-04-12 22:55 ` Zac Medico
2010-04-16 20:00 ` James Cloos
2010-04-12 22:47 ` Zac Medico
2010-04-16 20:23 ` James Cloos
2010-04-16 20:28 ` Ciaran McCreesh
2010-04-17 3:30 ` Steev Klimaszewski
2010-04-17 7:13 ` Ciaran McCreesh
2010-04-18 3:28 ` James Cloos
2010-04-18 7:45 ` Ciaran McCreesh
2010-04-19 20:59 ` James Cloos
2010-04-19 21:46 ` Harald van Dijk
2010-04-23 15:14 ` James Cloos
2010-04-25 6:16 ` Zac Medico
2010-04-03 10:33 ` [gentoo-dev] " Torsten Veller
2010-04-04 8:25 ` Michael Higgins
2010-04-06 14:27 ` James Cloos
2010-04-06 14:52 ` Duncan
2010-04-10 0:40 ` James Cloos
2010-04-06 14:25 ` James Cloos
2010-04-06 16:00 ` Michał Górny
2010-04-10 0:34 ` James Cloos
2010-04-17 20:07 ` Torsten Veller
2010-04-12 8:07 ` Christian Faulhammer
2010-04-12 9:03 ` Fabian Groffen
2010-04-20 6:49 ` Torsten Veller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100402001731.GO11663@hrair \
--to=ferringb@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
--cc=zmedico@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox