public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] perl eclass review - EAPI=3 + new helper eclass
Date: Sat, 17 Apr 2010 08:13:41 +0100	[thread overview]
Message-ID: <20100417081341.0c117967@snowmobile> (raw)
In-Reply-To: <m2j6d2ed5bd1004162030mabb8134sf19feac0afeb04ad@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]

On Fri, 16 Apr 2010 22:30:46 -0500
Steev Klimaszewski <steev@gentoo.org> wrote:
> On Fri, Apr 16, 2010 at 3:28 PM, Ciaran McCreesh
> <ciaran.mccreesh@googlemail.com> wrote:
> > On Fri, 16 Apr 2010 16:23:48 -0400
> > James Cloos <cloos@jhcloos.com> wrote:
> >> OK.  Let me rephrase.  Portage does not need to validate local
> >> changes.
> >
> > Sure it does. If it doesn't, and your local changes affect metadata,
> > horrible things happen.
> 
> Why not check the mtime on the overlay, if it is older than last sync
> time, not invalid.

Because it can still be invalid if you do that. If you're using a repo
with pregenerated cache with an eclass from a different repo than the
one used do the pregenerating, the pregenerated cache is always invalid.

> >> If a user uses a local eclass to override one in portage or in some
> >> remote overlay s/he follows, it is his/er responsibility to update
> >> it when the original undergoes major renovation.
> >
> > Users aren't responsible...
> 
> And doing everything we can to make them not be isn't going to teach
> them anything.

Which is why you design a system that just gets things right, rather
than one that relies upon users getting things right.

-- 
Ciaran McCreesh

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-04-17  7:14 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
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 [this message]
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=20100417081341.0c117967@snowmobile \
    --to=ciaran.mccreesh@googlemail.com \
    --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