From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15283 invoked by uid 1002); 3 Jul 2003 08:41:52 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 471 invoked from network); 3 Jul 2003 08:41:52 -0000 From: Philippe =?ISO-8859-1?Q?Lafoucri=E8re?= Reply-To: lafou@wanadoo.fr To: Gentoo-dev Content-Type: text/plain Organization: InFuzzion Message-Id: <1057221710.2355.9.camel@biproc> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4- Date: 03 Jul 2003 10:41:50 +0200 Content-Transfer-Encoding: 7bit Subject: [gentoo-dev] metadata.xml - emerge rsync X-Archives-Salt: 5ab30f2d-6bf7-4241-ae2d-8c94ad197920 X-Archives-Hash: ec731f9afd5d941c1d72175830bcefce Hi all, I'am just wondering about something. I've red here that emerge rsync causes some bandwidth problems. Why don't use a general metadata.xml file which contains all metadata about ebuilds. This could be (sorry for the fast & dirty exemple): [...] [...] MyEbuild-v0.1-r1 MyEbuild-v0.1-r2 MyEbuild-v0.1-r3 ... This file could be automaintened with all metadata.xml, and ebuilds present in repository. Then, an emerge rsync would get a gzipped version of this file, gunzip it, and make a diff with the local file. It can remove old ebuilds, and fetch the new ones (maybe gzipped too !). I hope I was clear, my english is not what it used to be :) Philippe -- gentoo-dev@gentoo.org mailing list