From mboxrd@z Thu Jan 1 00:00:00 1970
Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org)
by finch.gentoo.org with esmtp (Exim 4.60)
(envelope-from <gentoo-council+bounces-678-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1N7W0g-0005xm-E3
for garchives@archives.gentoo.org; Mon, 09 Nov 2009 15:18:26 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id C11B0E0B33;
Mon, 9 Nov 2009 15:18:25 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
by pigeon.gentoo.org (Postfix) with ESMTP id 96609E0B33
for <gentoo-council@lists.gentoo.org>; Mon, 9 Nov 2009 15:18:25 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp.gentoo.org (Postfix) with ESMTP id EC76567D88
for <gentoo-council@lists.gentoo.org>; Mon, 9 Nov 2009 15:18:24 +0000 (UTC)
X-Virus-Scanned: amavisd-new at gentoo.org
X-Spam-Score: -1.96
X-Spam-Level:
X-Spam-Status: No, score=-1.96 required=5.5 tests=[AWL=0.639, BAYES_00=-2.599]
Received: from smtp.gentoo.org ([127.0.0.1])
by localhost (smtp.gentoo.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id z2m-cJkbcjNL for <gentoo-council@lists.gentoo.org>;
Mon, 9 Nov 2009 15:18:18 +0000 (UTC)
Received: from mail-ew0-f216.google.com (mail-ew0-f216.google.com [209.85.219.216])
by smtp.gentoo.org (Postfix) with ESMTP id D89C867DA0
for <gentoo-council@gentoo.org>; Mon, 9 Nov 2009 15:18:17 +0000 (UTC)
Received: by ewy12 with SMTP id 12so3349905ewy.0
for <gentoo-council@gentoo.org>; Mon, 09 Nov 2009 07:18:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:sender:received:in-reply-to
:references:date:x-google-sender-auth:message-id:subject:from:to
:content-type;
bh=iDhQTzMHmJ4odb4xjDm+wZpnB54ZUrOeNN5z4hw8LDg=;
b=ACzkLykGasvDxCyTWmQSQ6VgpMexbgz7epTqncqhyZtM/FC4n3ZJPSdLKTwqrN2/Yt
vMUqRT4phs1FsVAvX8+Cgh6yBadYx+ffMFUHm+yH0gVkQH/09gAbzDIxIM6zEQ80u43Q
v4xQ2foqG94N1ZappvI0g7jWCMXCpI1ZhFdhs=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=mime-version:sender:in-reply-to:references:date
:x-google-sender-auth:message-id:subject:from:to:content-type;
b=NPU8za04CDav3r/bFX9OUDpK+SSpSK/KcAoflSygJ72AaOBtpy/wK4xj/t5E4P2PF0
MS92F3jbAk12mL+k+XQuUYLWLENaXY4g/e9LqC1u67MUa9nBjvK+3No/XaPIQRZNMk7S
wzkhkSgUL3k9wvj34/zQFRS1CVeavoWXRlu8Q=
Precedence: bulk
List-Post: <mailto:gentoo-council@lists.gentoo.org>
List-Help: <mailto:gentoo-council+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-council+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-council+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-council.gentoo.org>
X-BeenThere: gentoo-council@lists.gentoo.org
MIME-Version: 1.0
Sender: denis.dupeyron@gmail.com
Received: by 10.216.89.10 with SMTP id b10mr2665063wef.182.1257779895711; Mon,
09 Nov 2009 07:18:15 -0800 (PST)
In-Reply-To: <20091108191439.3fcee79d@snowcone>
References: <19184.25176.380022.392451@a1i15.kph.uni-mainz.de>
<20091103180632.0eb8e26c@snowcone>
<19185.39090.798573.758417@a1i15.kph.uni-mainz.de>
<20091104152835.369e3e18@snowcone>
<19186.42949.760878.199957@a1i15.kph.uni-mainz.de>
<20091108191439.3fcee79d@snowcone>
Date: Mon, 9 Nov 2009 08:18:15 -0700
X-Google-Sender-Auth: ab8bf3935d0da0f7
Message-ID: <7c612fc60911090718y144319f5lc9827a5e2e153c2@mail.gmail.com>
Subject: Re: [gentoo-council] Re: mtime preservation
From: Denis Dupeyron <calchan@gentoo.org>
To: gentoo-council@lists.gentoo.org
Content-Type: text/plain; charset=ISO-8859-1
X-Archives-Salt: 7b78eb3c-fde1-447e-8fd6-7d1879f9d2cc
X-Archives-Hash: 3aa104fd59478dd0e9ad71de6bbe7692
Let the clueless dev that I am summarize the situation. Please correct
me if I'm wrong, I think that will help more people than just me. In
the end I'll propose 2 wordings for PMS.
I understand that the issue with requiring mtime preservation is that
after unpacking the tarball(s) some files can have absurd dates, like
January 1st 1970 or else. One easy solution to this would be to reset
mtimes at merge time which will take care of everything. However, I
know of a package which requires mtime preservation from src_compile
to the moment it's merged to ${ROOT}. And if there's a package like
this in my very small corner of Gentoo there must be more elsewhere,
and there probably will be more in the future.
So here are the 2 wordings I propose.
1 - All mtimes from the package's sources are preserved until files
are merged to ${ROOT}. In case some mtimes are absurd and/or
unsuitable, they're considered a bug and it's the maintainer's
responsibility to fix them and report back upstream.
2 - All mtimes from the package's sources are reset to current time
between the src_unpack phase and the next one. That is before
src_configure when EAPI<2 and before src_prepare when EAPI>=2. mtimes
are then preserved until files are merged to ${ROOT}.
How's that? Am I missing something?
Denis.