From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1LWIMM-0000xS-Vq for garchives@archives.gentoo.org; Sun, 08 Feb 2009 22:42:43 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id DD75DE0465; Sun, 8 Feb 2009 22:42:39 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id B8715E0465 for ; Sun, 8 Feb 2009 22:42:39 +0000 (UTC) Received: from [192.168.22.10] (ip68-4-152-120.oc.oc.cox.net [68.4.152.120]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 48BA4651DA for ; Sun, 8 Feb 2009 22:42:39 +0000 (UTC) Message-ID: <498F5FF5.50203@gentoo.org> Date: Sun, 08 Feb 2009 14:43:01 -0800 From: Zac Medico User-Agent: Thunderbird 2.0.0.19 (X11/20081209) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [RFC] DIGESTS metadata variable for cache validation References: <498758E6.5080609@gentoo.org> <1234045916.24784.1373.camel@localhost> <498E17E6.8060407@gentoo.org> <20090208221814.722f573a@snowmobile> In-Reply-To: <20090208221814.722f573a@snowmobile> X-Enigmail-Version: 0.95.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Archives-Salt: 001e9d8c-0298-4a97-916e-aa90a8109049 X-Archives-Hash: b9f46173550b9e8d78bc1af892ac34aa -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Ciaran McCreesh wrote: > On Sat, 07 Feb 2009 15:23:18 -0800 > Zac Medico wrote: >>> Well, usually you don't keep intermediate or generated files in a >>> VCS, so why the metadata? >> People who distribute overlays commonly ask if it's possible to >> distribute metadata cache with the overlay. Using a format that >> doesn't rely on timestamps will allow them to distribute metadata >> cache using their existing infrastructure, which is typically git or >> subversion. In addition to overlays, it would also be useful for >> forks of the entire gentoo tree, such as the funtoo tree [1]. > > Are these people really all going to remember to run some command at > the top level of the repository before every commit, and to git add the > relevant files for everything (thus making really messy commits)? The cache can be incrementally updated by a tool such as repoman, or it can be updated in periodic batches by a cron job. The periodic batch approach may be more convenient for eclass changes affect large numbers of ebuilds. > Sticking metadata cache files under version control really is a perfect > example of doing it wrong... Well, if you want to use timestamps, the alternative is to distributors to use a protocol which preserves timestamps. This creates an unnecessary burden. Allowing distribution of metadata cache via version control systems is more flexible. - -- Thanks, Zac -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkmPX/QACgkQ/ejvha5XGaMPewCeOZYsNt2bv+CbOV58aV7isq4f wCAAnA/10jcuad5NrP3BxyFZAYWH07ot =iRw3 -----END PGP SIGNATURE-----