public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: David Leverton <levertond@googlemail.com>
Cc: gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] Agenda for the meeting of December 7th, 2009
Date: Sun, 6 Dec 2009 15:05:59 +0100	[thread overview]
Message-ID: <19227.47687.44279.886421@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <200912061240.29793.levertond@googlemail.com>

>>>>> On Sun, 6 Dec 2009, David Leverton wrote:

> The intention is to make the spec for a new EAPI unnecessarily
> complex, just to avoid changing an existing implementation?

The spec first proposed was along the lines "mtime is updated if
(and only if) the package manager modifies the file" [1], but the
Paludis party raised objections that this was not specific enough.
But see below about "common sense".

>> We should also consider including this in EAPI 0 retroactively

> Doing things like that defeats the purpose of EAPI.

Normally I would agree with this. However, in this particular case the
damage has already been done. We wouldn't break anything by applying
this retroactively. The breakage of packages will go away in the
moment when all package managers preserve mtimes, independent of what
we write into the spec. So we could as well keep it simple (i.e.
without distinction between EAPIs).

> People are expected to use common-sense when reading it (since we
> don't have enough man-power to make it completely airtight), [...]

I fully agree. If such wisdom had been used earlier, the whole issue
would long be off the stove.

Ulrich

[1] <http://bugs.gentoo.org/264130#c41>



  reply	other threads:[~2009-12-06 14:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-06  7:40 [gentoo-council] Agenda for the meeting of December 7th, 2009 Denis Dupeyron
2009-12-06 11:48 ` Ulrich Mueller
2009-12-06 12:40   ` David Leverton
2009-12-06 14:05     ` Ulrich Mueller [this message]
2009-12-06 14:27       ` David Leverton
2009-12-06 17:18   ` Robin H. Johnson
2009-12-06 19:04     ` Denis Dupeyron
2009-12-06 19:51 ` Ned Ludd
2009-12-07  3:48 ` Zac Medico

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=19227.47687.44279.886421@a1i15.kph.uni-mainz.de \
    --to=ulm@gentoo.org \
    --cc=gentoo-council@lists.gentoo.org \
    --cc=levertond@googlemail.com \
    /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