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-dev+bounces-38562-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1NDPCZ-0000dY-VA
for garchives@archives.gentoo.org; Wed, 25 Nov 2009 21:15:04 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id F0E49E09F1;
Wed, 25 Nov 2009 21:14:06 +0000 (UTC)
Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183])
by pigeon.gentoo.org (Postfix) with ESMTP id CDD2BE09F1
for <gentoo-dev@lists.gentoo.org>; Wed, 25 Nov 2009 21:14:06 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp.gentoo.org (Postfix) with ESMTP id 6C73567B74
for <gentoo-dev@lists.gentoo.org>; Wed, 25 Nov 2009 21:14:06 +0000 (UTC)
X-Virus-Scanned: amavisd-new at gentoo.org
X-Spam-Score: -1.968
X-Spam-Level:
X-Spam-Status: No, score=-1.968 required=5.5 tests=[AWL=0.631,
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 uednHbd6qWjp for <gentoo-dev@lists.gentoo.org>;
Wed, 25 Nov 2009 21:14:00 +0000 (UTC)
Received: from mail-fx0-f228.google.com (mail-fx0-f228.google.com [209.85.220.228])
by smtp.gentoo.org (Postfix) with ESMTP id 998CE6754C
for <gentoo-dev@gentoo.org>; Wed, 25 Nov 2009 21:13:59 +0000 (UTC)
Received: by fxm28 with SMTP id 28so133877fxm.25
for <gentoo-dev@gentoo.org>; Wed, 25 Nov 2009 13:13:58 -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=Xwdwu7Wd1v1EzMzkBDhHRzxssakyAbrprxaMgCWjCpE=;
b=JiRYg/Hx3S5rKobOkg6bkahrSIAG3PDuhUeg/CsMQa72IMYXYKBofrzlDv4QnNimwg
2v5F6rjwrizMETHhdgjRIfWg2vBhzh64rVKJQy48EeT6V8Rvacjz/HKf1Us+JsJX0+Ef
69K7nUSZn+4yWrNw/KceWKkYouEyuGEVIYMNA=
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=pdhfg04LHXm2E+rMAXykgoEpaKo6xEdtm3XN8TioaZZFetBw43sfd3q5EuhH29rcn5
I0s/jtUFC6P+SzFht1dgANJdjx4hfQUS8OB2937UEcsjuhYw11EfBtXiKQD3i22O7f5a
0ADEItg1jDoOKt626xUK1bIPCrC4jHZdSfHuc=
Precedence: bulk
List-Post: <mailto:gentoo-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-dev.gentoo.org>
X-BeenThere: gentoo-dev@lists.gentoo.org
Reply-to: gentoo-dev@lists.gentoo.org
MIME-Version: 1.0
Sender: denis.dupeyron@gmail.com
Received: by 10.216.89.8 with SMTP id b8mr72976wef.180.1259183638237; Wed, 25
Nov 2009 13:13:58 -0800 (PST)
In-Reply-To: <7c612fc60911231049n4a51ddb0u30ae72d8ed93cdec@mail.gmail.com>
References: <19184.25176.380022.392451@a1i15.kph.uni-mainz.de>
<20091108191439.3fcee79d@snowcone>
<7c612fc60911090718y144319f5lc9827a5e2e153c2@mail.gmail.com>
<20091109153429.502e272f@snowcone>
<19193.4389.637969.727075@a1i15.kph.uni-mainz.de>
<20091119221248.539eedd9@snowmobile>
<7c612fc60911191614h5e37c849y50ad217a828fa744@mail.gmail.com>
<20091120001820.7274bdf7@snowmobile> <4B07362D.2010108@gentoo.org>
<7c612fc60911231049n4a51ddb0u30ae72d8ed93cdec@mail.gmail.com>
Date: Wed, 25 Nov 2009 14:13:58 -0700
X-Google-Sender-Auth: e766c006232a4e7f
Message-ID: <7c612fc60911251313i705a182as6cf50402c7829beb@mail.gmail.com>
Subject: [gentoo-dev] Re: mtime preservation
From: Denis Dupeyron <calchan@gentoo.org>
To: gentoo-dev <gentoo-dev@lists.gentoo.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Archives-Salt: 09b89f5d-fb3d-45a8-9f81-09cd1252ba31
X-Archives-Hash: cc4b3c4efa37d7a933cc94fd224ef092
A quick note to tell you that I have tried to look for examples of
breakage due to how mtime preservation is currently implemented in
portage. Unfortunately I didn't find anything, maybe because I'm not
knowledgeable enough or because I can't afford to spend any more time
on this. If any of you can provide an example then please do so.
In case nobody could show any sign of such breakage I would have to
add to the list of two propositions to vote on:
3- Do nothing.
We can always point to code that shows the implementation is
suboptimal but we have to understand that some of us who are less
proactive at fixing issues may want to procrastinate until breakage
actually happens.
Denis.