public inbox for gentoo-council@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] Agenda (draft) for November meeting 2009-11-09
Date: Tue, 3 Nov 2009 23:10:23 +0000	[thread overview]
Message-ID: <20091103231023.43d4fca7@snowmobile> (raw)
In-Reply-To: <7c612fc60911031456w63621525n65a9d018f46e88cb@mail.gmail.com>

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

On Tue, 3 Nov 2009 15:56:39 -0700
Denis Dupeyron <calchan@gentoo.org> wrote:
> Could the both of you please flesh out a proposal on how you'd expect
> the council to solve these issues? It would best if, on top of telling
> what should be done, you explained why it should be done this way.
> Raising the questions is already interesting but proposing answers is
> even better. You may have done that elsewhere before but summarizing
> it here would help tremendously.

Ok. For this:

> > "Agree upon a wording for PMS for the mtime modification change
> > introduced to EAPI 3 last time"

I honestly don't have an answer to this, nor a preferred solution. So
far as I can see, any possible solution is hit by one of:

* requiring changes to Portage.

* preventing future changes to Portage that would clearly be useful
  (for example, shebang rewriting for Prefix).

* being so vague and unspecific that it is entirely legal for package
  managers not to implement mtime preservation at all.

Obviously the Council had something else in mind when they voted the
proposal in, but the combined wisdom of the PMS team hasn't managed to
work out what that is. Thus, I'd like the Council to explain their
decision in sufficiently precise language that I can convert it to
LaTeX for PMS, and implement it in Paludis.

> > I'd like council to discuss what I consider a major bug in PMS -
> > see the discussion at
> > http://archives.gentoo.org/gentoo-pms/msg_95a13d880eb521b13d7090f30350c26a.xml  

As for this one, I was hoping Patrick would, as asked, start a
discussion on the gentoo-dev list regarding backwards compatibility and
how much developers care about having a clean upgrade path. I gather
from the previous Council meeting and from other comments that at least
some developers consider not being able to upgrade from an older Gentoo
install as being a problem.

The question, really, is whether there not being an upgrade path is
deliberate, or whether it's an accident that needs fixing. I don't
think that's a decision that should be made without a general
discussion amongst all Gentoo developers, and I certainly don't think
it's a decision that should be made arbitrarily by the PMS editors.

-- 
Ciaran McCreesh

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

  reply	other threads:[~2009-11-03 23:10 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-03 17:03 [gentoo-council] Agenda (draft) for November meeting 2009-11-09 Ulrich Mueller
2009-11-03 18:06 ` Ciaran McCreesh
2009-11-04 15:07   ` [gentoo-council] mtime preservation (was: Agenda (draft) for November meeting 2009-11-09) Ulrich Mueller
2009-11-04 15:28     ` [gentoo-council] " Ciaran McCreesh
2009-11-04 21:12       ` [gentoo-council] Re: mtime preservation Zac Medico
2009-11-04 21:29         ` Ciaran McCreesh
2009-11-05  5:54           ` Zac Medico
2009-11-05  6:11             ` Ulrich Mueller
2009-11-05  6:18               ` Zac Medico
2009-11-05  9:11                 ` Ulrich Mueller
2009-11-05 10:24       ` Ulrich Mueller
2009-11-08 19:14         ` Ciaran McCreesh
2009-11-09 15:18           ` Denis Dupeyron
2009-11-09 15:34             ` Ciaran McCreesh
2009-11-09 15:42               ` Petteri Räty
2009-11-09 16:37               ` Ulrich Mueller
2009-11-09 16:53                 ` Ciaran McCreesh
2009-11-10  7:07               ` [gentoo-council] " Ulrich Mueller
2009-11-19 22:12                 ` Ciaran McCreesh
2009-11-20  0:14                   ` Denis Dupeyron
2009-11-20  0:18                     ` Ciaran McCreesh
2009-11-21  0:37                       ` Zac Medico
2009-11-23 19:16                   ` Ulrich Mueller
2009-11-09 16:36             ` [gentoo-council] " Ulrich Mueller
2009-11-09 17:58               ` Denis Dupeyron
2009-11-09 18:14                 ` Ciaran McCreesh
2009-11-09 18:48                   ` Denis Dupeyron
2009-11-03 20:17 ` [gentoo-council] Agenda (draft) for November meeting 2009-11-09 Patrick Lauer
2009-11-03 22:56   ` Denis Dupeyron
2009-11-03 23:10     ` Ciaran McCreesh [this message]
2009-11-03 23:14     ` Patrick Lauer
2009-11-04 15:19 ` Ulrich Mueller
2009-11-04 15:22   ` Denis Dupeyron
2009-11-05 20:44 ` Ulrich Mueller

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=20091103231023.43d4fca7@snowmobile \
    --to=ciaran.mccreesh@googlemail.com \
    --cc=gentoo-council@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