W. Trevor King posted on Mon, 15 Sep 2014 13:33:46 -0700 as excerpted: > On Mon, Sep 15, 2014 at 01:29:44PM -0700, W. Trevor King wrote: >> I don't see any benefit to using rsync vs. a shallow clone as the >> transmission protocol. > > Other than the fact that before you dropped it you'd need to push a > ‘emerge sync’ that could handle either rsync or Git, stabilize that > Portage, and then wait for folks to adopt it.
Portage already handles it. =:^) Quoting from the emerge (1) manpage (listed as v2.2.12, dated Mar 2014): --sync Updates repositories, for which sync-type and sync-uri attributes are set in repos.conf. See portage(5) for more information. Then in the portage (5) manpage: repos.conf Specifies site-specific repository configuration information. Configuration specified in repos.conf can be overriden by PORTAGE_REPOSITORIES environmental variable, which has the same format as repos.conf. [...] Attributes supported in sections of repositories: [...] sync-type Specifies type of synchronization performed by `emerge --sync`. Valid non-empty values: cvs, git, rsync This attribute can be set to empty value to disable synchronization of given repository. Empty value is default. sync-uri Specifies URI of repository used for synchronization performed by `emerge --sync`. This attribute can be set to empty value to disable synchronization of given repository. Empty value is default. Syntax: cvs: [cvs://]:access_method:[username@]hostname[:port]:/path git: (git|git+ssh|http|https)://[username@]hostname[:port]/path rsync: (rsync|ssh)://[username@]hostname[:port]/(module|path) So portage already handles it. =:^) Tho it's possible there are still bugs as surely that doesn't have the extremely broad long-term testing that rsync does, and I'm ~arch of course and don't know if that's stable, yet. But it's there. -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman