public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Zac Medico <zmedico@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] perl eclass review - EAPI=3 + new helper eclass
Date: Tue, 06 Apr 2010 11:39:26 -0700	[thread overview]
Message-ID: <4BBB7FDE.7090306@gentoo.org> (raw)
In-Reply-To: <m36344slr9.fsf@lugabout.jhcloos.org>

On 04/06/2010 07:22 AM, James Cloos wrote:
>>>>>> "ZM" == Zac Medico <zmedico@gentoo.org> writes:
> 
> ZM> You can configure eclass override behavior via eclass-overrides in
> ZM> /etc/portage/repos.conf, as documented in `man portage`.
> 
> ,----< From that manpage >
> | When using eclass-overrides, due to bug #276264, you must ensure that
> | your portage tree does not contain a metadata/cache/ directory.
> `----
> 
> Which translates into "eclass-orderrides are completely and entirely
> useless, so don't bother.

Well, it's roughly equivalent to the old default behavior (which you
apparently preferred). However, the issue is now complicated by the
fact that FEATURES=metadata-transfer is disabled by default, so when
portage goes to pull cache directly from metadata/cache/, it won't
be able to validate eclass changes since there are no eclass
timestamps saved inside metadata/cache/. FWIW, there was some
discussion about extending the cache format to improve
the validation mechanism for eclasses here:

http://archives.gentoo.org/gentoo-dev/msg_cfa80e33ee5fa6f854120ddfb9b468b3.xml

> Portage used to used to search for eclasses starting in the top overlay;
> it should not have changed.

Well, the biggest caveat to that behavior is that it tends to
invalidate metadata cache as reported in this bug:

  http://bugs.gentoo.org/show_bug.cgi?id=124041

I'd be happy to work on resolving issues with eclass-orderrides to
make it more usable. However, due to the need to regenerate metadata
cache, I don't think that this is something that can ever again be
enabled by default.
-- 
Thanks,
Zac



  reply	other threads:[~2010-04-06 18:39 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
2010-04-02  0:25       ` Zac Medico
2010-04-06 14:22     ` James Cloos
2010-04-06 18:39       ` Zac Medico [this message]
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=4BBB7FDE.7090306@gentoo.org \
    --to=zmedico@gentoo.org \
    --cc=gentoo-dev@lists.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