| 1 |
On Tue, Sep 16, 2014 at 05:35:08PM +0000, Duncan wrote: |
| 2 |
> W. Trevor King posted on Mon, 15 Sep 2014 13:33:46 -0700 as excerpted: |
| 3 |
> > On Mon, Sep 15, 2014 at 01:29:44PM -0700, W. Trevor King wrote: |
| 4 |
> >> I don't see any benefit to using rsync vs. a shallow clone as the |
| 5 |
> >> transmission protocol. |
| 6 |
> > |
| 7 |
> > Other than the fact that before you dropped it you'd need to push a |
| 8 |
> > ‘emerge sync’ that could handle either rsync or Git, stabilize that |
| 9 |
> > Portage, and then wait for folks to adopt it. |
| 10 |
> |
| 11 |
> Portage already handles it. =:^) |
| 12 |
|
| 13 |
Oh, lovely :). Looks like that landed in 2.2.0 with 47e8d22d (Add |
| 14 |
support for multiple repositories in `emerge --sync`, 2013-07-23). |
| 15 |
There are older Portages in the tree though (back to 2.1.6.7_p1), so |
| 16 |
you'd still want to wait until those were gone before dropping rsync. |
| 17 |
|
| 18 |
Also, I don't see a way to say “use Git to sync, but keep a shallow |
| 19 |
repository”. Ideally, we'd want: |
| 20 |
|
| 21 |
$ git clone --depth=1 git://git.gentoo.org/gentoo-portage.git |
| 22 |
|
| 23 |
for the initial clone (modulo whatever URI), and: |
| 24 |
|
| 25 |
$ git pull --depth=1 |
| 26 |
|
| 27 |
for subsequent syncs. pym/_emerge/actions.py currently hardcodes ‘git |
| 28 |
pull’ for the latter, and doesn't seem to have any code for the |
| 29 |
former. On the other hand, it wouldn't be too terrible to force users |
| 30 |
to shallow their history manually whenever they felt like it. |
| 31 |
|
| 32 |
Cheers, |
| 33 |
Trevor |
| 34 |
|
| 35 |
-- |
| 36 |
This email may be signed or encrypted with GnuPG (http://www.gnupg.org). |
| 37 |
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy |
Archives