From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-council@lists.gentoo.org
Subject: Re: [gentoo-council] Re: [gentoo-dev-announce] Agenda for October meeting next Monday 2009-10-12
Date: Sat, 10 Oct 2009 19:05:30 +0100 [thread overview]
Message-ID: <20091010190530.7470d43f@snowmobile> (raw)
In-Reply-To: <1255197258.5783.8.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 1534 bytes --]
On Sat, 10 Oct 2009 10:54:18 -0700
Ned Ludd <solar@gentoo.org> wrote:
> Luca's and Zac's comments work for me.
>
> Either PMS seems to be about documenting ebuild syntax. If we force
> in a change for mtimes then it's no different than forcing a given
> syntax for VDB/binpkg handling etc. And I have a feeling we don't
> really want to open that can of worms.
Uhm. Two things.
First: this is not about existing syntax. Different Portage versions do
different things with mtimes, so currently ebuilds can't rely upon any
particular behaviour. The proposal is about standardising behaviour for
EAPI 3, which would allow EAPI 3 ebuilds to rely upon mtimes being
handled in a particular way. The previous Council rejected this
proposal, but Ulrich wants it reconsidered. If it is reconsidered, the
question is what behaviour we want to standardise. Going with "what
Portage does" is undesirable for two reasons -- first, it leads to
files with timestamps like 1 Jan 1970 being merged to /, and second,
it's undefined behaviour for any file that's modified by the package
manager (e.g. for stripping, fixing WORKDIR mentions, compressing docs,
repairing QA violations and so on -- there are currently no restrictions
on what a package manager can tidy up).
Second, VDB and binary packages have nothing to do with PMS.
If you just want to document "what Portage does", then PMS and EAPI 3
need no changes, since "what Portage does" depends upon what Portage
version you're using.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-10-10 18:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 20:13 [gentoo-council] Agenda for October meeting next Monday 2009-10-12 Petteri Räty
2009-10-09 20:56 ` Roy Bamford
2009-10-09 21:32 ` Ned Ludd
2009-10-09 22:35 ` Ciaran McCreesh
2009-10-09 22:35 ` Roy Bamford
2009-10-09 21:53 ` [gentoo-council] Re: [gentoo-dev-announce] " Ulrich Mueller
2009-10-09 22:02 ` Luca Barbato
2009-10-09 22:20 ` Ulrich Mueller
2009-10-10 17:54 ` Ned Ludd
2009-10-10 18:05 ` Ciaran McCreesh [this message]
2009-10-10 18:29 ` Ulrich Mueller
2009-10-10 18:36 ` Ciaran McCreesh
2009-10-10 19:27 ` Petteri Räty
2009-10-14 6:08 ` [gentoo-council] " Zac Medico
2009-10-14 6:20 ` Ned Ludd
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=20091010190530.7470d43f@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