[gentoo-dev] metadata.xml - emerge rsync

["Philippe Lafoucrière" <lafou@wanadoo.fr>]

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):

<root>
	<dev-python desc="Dev tools for python">
		<somepackage desc="python tool for ...">

			<pkgmetadata>[...]</pkgmetadata>

			<herd>[...]</herd>
			
			<ebuild>MyEbuild-v0.1-r1</ebuild>
			<ebuild>MyEbuild-v0.1-r2</ebuild>
			<ebuild stat="masked">MyEbuild-v0.1-r3</ebuild>
		</somepackage>
	</dev-python>
	<other-category>
		...
	</other-category>
</root>

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