From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1NxUhM-0001kq-Lt for garchives@archives.gentoo.org; Fri, 02 Apr 2010 00:25:20 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 45BFAE07BD; Fri, 2 Apr 2010 00:25:17 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id DA1C0E07AF for ; Fri, 2 Apr 2010 00:25:09 +0000 (UTC) Received: from [192.168.22.10] (ip68-4-152-120.oc.oc.cox.net [68.4.152.120]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 598201B4009 for ; Fri, 2 Apr 2010 00:25:09 +0000 (UTC) Message-ID: <4BB5396E.1000009@gentoo.org> Date: Thu, 01 Apr 2010 17:25:18 -0700 From: Zac Medico User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); en-US; rv:1.9.1.8) Gecko/20100315 Thunderbird/3.0.3 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] perl eclass review - EAPI=3 + new helper eclass References: <20100330111154.GA28735@veller.net> <4BB536DC.8090405@gentoo.org> <20100402001731.GO11663@hrair> In-Reply-To: <20100402001731.GO11663@hrair> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: bbc777c8-0410-4a2a-883e-5e26ac630f65 X-Archives-Hash: 2822aea55073d0f36f4b2fda693c045f On 04/01/2010 05:17 PM, Brian Harring wrote: > 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. I think it would be preferable to extend the cache format to improve the validation mechanism, as discussed here: http://archives.gentoo.org/gentoo-dev/msg_cfa80e33ee5fa6f854120ddfb9b468b3.xml That said, I wouldn't be opposed to adding something like the REPO_OPTIONS='exclude-cache' approach that you suggest. -- Thanks, Zac