public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-dev] metadata.xml - emerge rsync
@ 2003-07-03  8:41 Philippe Lafoucrière
  2003-07-03 12:16 ` [gentoo-dev] " Heinrich Wendel
  0 siblings, 1 reply; 2+ messages in thread
From: Philippe Lafoucrière @ 2003-07-03  8:41 UTC (permalink / raw
  To: Gentoo-dev

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


^ permalink raw reply	[flat|nested] 2+ messages in thread

* [gentoo-dev] Re: metadata.xml - emerge rsync
  2003-07-03  8:41 [gentoo-dev] metadata.xml - emerge rsync Philippe Lafoucrière
@ 2003-07-03 12:16 ` Heinrich Wendel
  0 siblings, 0 replies; 2+ messages in thread
From: Heinrich Wendel @ 2003-07-03 12:16 UTC (permalink / raw
  To: gentoo-dev

Philippe Lafoucrière wrote:

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

I don't see the advantage of this method, as rsync only fetches files that
were changed.

> 
> Philippe
mfg, Heinrich :)

> 
> 
> --
> gentoo-dev@gentoo.org mailing list



--
gentoo-dev@gentoo.org mailing list


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-07-03 12:16 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-07-03  8:41 [gentoo-dev] metadata.xml - emerge rsync Philippe Lafoucrière
2003-07-03 12:16 ` [gentoo-dev] " Heinrich Wendel

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox