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-soc+bounces-950-garchives=archives.gentoo.org@lists.gentoo.org>)
id 1OJOWg-0003pN-K9
for garchives@archives.gentoo.org; Tue, 01 Jun 2010 10:16:50 +0000
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id 2A729E0A7D;
Tue, 1 Jun 2010 10:16:42 +0000 (UTC)
Received: from mail-pw0-f53.google.com (mail-pw0-f53.google.com [209.85.160.53])
by pigeon.gentoo.org (Postfix) with ESMTP id ED5A8E0A7D
for <gentoo-soc@lists.gentoo.org>; Tue, 1 Jun 2010 10:16:41 +0000 (UTC)
Received: by pwj8 with SMTP id 8so1196385pwj.40
for <gentoo-soc@lists.gentoo.org>; Tue, 01 Jun 2010 03:16:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=gamma;
h=domainkey-signature:mime-version:received:received:in-reply-to
:references:date:message-id:subject:from:to:content-type;
bh=Dbf8y9LEwAl5SzsKh4Sc/umSXDVHgJkbFQvCfsDd7uo=;
b=KjdchxV4YigB++g3dvxT83Zd2kuIUkYuU+QKirJo7fD/YtuwL3Ub64cv3LoU37S1ve
rpyMd67g/Z+sfwoQECku7Ae79vdSfCezpM98Pq5MTOVWRlVc3A0YMdO7uUAUi65rCLpr
Ko4n4Kz7bwirI80q/ByQrjxnsOrufsmT82yMo=
DomainKey-Signature: a=rsa-sha1; c=nofws;
d=gmail.com; s=gamma;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type;
b=nC2lYsX7KxVEVRXweS3Q/JkMSLiArvB4QATLXMOtymqzJ/piybAEVLQ7JsGvZKHZ4g
/N8rrleItKiGEOzzzTtDz3qaQIiYpMRsP75L/3IiC2CkjolR2LxUK2Js0KQ3BEGKJ9zN
EZCWFVuNeRyOdTce2SKSVB8QUMB29HGwOUs0A=
Precedence: bulk
List-Post: <mailto:gentoo-soc@lists.gentoo.org>
List-Help: <mailto:gentoo-soc+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-soc+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-soc+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-soc.gentoo.org>
X-BeenThere: gentoo-soc@lists.gentoo.org
Reply-to: gentoo-soc@lists.gentoo.org
MIME-Version: 1.0
Received: by 10.140.58.21 with SMTP id g21mr4297151rva.234.1275387401346; Tue,
01 Jun 2010 03:16:41 -0700 (PDT)
Received: by 10.140.203.18 with HTTP; Tue, 1 Jun 2010 03:16:41 -0700 (PDT)
In-Reply-To: <AANLkTilCT9R5FJKeoPh7Hk1ikOUcrh8ZNGARJCcMlw9Y@mail.gmail.com>
References: <1275376236.31167.11.camel@chi>
<AANLkTilCT9R5FJKeoPh7Hk1ikOUcrh8ZNGARJCcMlw9Y@mail.gmail.com>
Date: Tue, 1 Jun 2010 15:46:41 +0530
Message-ID: <AANLkTin6N7LXvRekWr6WR1wxV1u0rG-p_8ZzhMQDiDLb@mail.gmail.com>
Subject: Re: [gentoo-soc] Project Grumpy - weekly report #1
From: Nirbheek Chauhan <nirbheek.chauhan@gmail.com>
To: gentoo-soc@lists.gentoo.org
Content-Type: text/plain; charset=UTF-8
X-Archives-Salt: ea3841cd-98bb-4d9a-8908-b7243b5a7a3a
X-Archives-Hash: 73434817d2c5f7ea06ef763e3e911dc8
On Tue, Jun 1, 2010 at 1:41 PM, Arun Raghavan <arunissatan@gmail.com> wrote:
> On 1 June 2010 12:40, Priit Laes <plaes@plaes.org> wrote:
> [...]
>> Anyway, I'll leave this idea simmering here for a while and unless
>> someone comes up with a better idea (Yes, I have also thought about
>> scanning whole portage tree every x-hours), I'm going to implement the
>> daemon.
>
> My 2p - I don't see a major advantage of a monitoring daemon over a
> periodic full-scan, or caching the mtimes. IMO that the latter options
> are better on the grounds that you're not introducing an additional
> entity (Occam's Razor, KISS, etc. etc.), and afaics there is no
> significant gain of the daemon - inotify watches are not going to
> imply immediate updates since your tree updates will be periodic
> anyway.
>
I agree with Arun here, you can easily schedule the server to run the
grumpy update whenever an eix-sync (or cvs up) is done. No point
running a monitoring daemon when you know exactly when something will
be updated.
--
~Nirbheek Chauhan
Gentoo GNOME+Mozilla Team