1 |
Vadim A. Misbakh-Soloviov posted on Wed, 24 Feb 2016 10:38:55 +0600 as |
2 |
excerpted: |
3 |
|
4 |
>> Is this actually true? For the typical use case of daily or close to |
5 |
>> daily updates I'd think that git would be much more efficient. |
6 |
|
7 |
> As there were noticed multiple times on the list already, this should |
8 |
> not ever happen, at least, until git will support resumable |
9 |
> fetches/clones/whatever. Otherwise you'll make a lot of people, using |
10 |
> bad quality internet access, to frustrate. |
11 |
|
12 |
[I was confused at first as your response has little or nothing to do |
13 |
with the bit you quoted, but rather, with the idea of switching from |
14 |
rsync to git, in general.] |
15 |
|
16 |
While I agree that git not being able to resume is certainly a serious |
17 |
pain for those with unreliable connections, they should be able to switch |
18 |
to webrsync, should the rsync method itself be deprecated. As I've said, |
19 |
git syncing can't replace webrsync security, so webrsync will need to |
20 |
stay around for the foreseeable future. |
21 |
|
22 |
Meanwhile, deprecated doesn't necessarily mean shut down or entirely |
23 |
unsupported. Indeed, the implication is that it continues to stay around |
24 |
for quite some time, or rsync (or at least support for it) would be |
25 |
dropped, not deprecated. It simply means that the handbook, etc, will |
26 |
stress non-deprecated alternatives instead of deprecated ones, and that |
27 |
over a period of years, the need for rsync mirrors will go down such that |
28 |
eventually, perhaps one per region/continent will suffice, and perhaps |
29 |
ultimately, only one period, instead of the multiple per continent we |
30 |
tend to have now. |
31 |
|
32 |
Most of the others would presumably be converted to git and tarball |
33 |
mirror resources, with a few converted to webrsync instead, since it'll |
34 |
no doubt get some uptick in usage as rsync fades out. |
35 |
|
36 |
But given the installed base and the number of folks already using rsync |
37 |
that wouldn't see a reason to change, this deprecation and phase down |
38 |
would be on the scale of years, three years at absolute minimum I |
39 |
suppose, and more likely 5-10 years. |
40 |
|
41 |
Do you realize just how long 10 years is in Linux distro terms? Gentoo's |
42 |
certainly past that now, but who knows what will happen in ten years? |
43 |
Gentoo itself may no longer be around by then, or maybe it'll be around, |
44 |
but will only have enough users for a single mirror or two. Or maybe |
45 |
hardware advances will be such that building from sources will be trivial |
46 |
by then and gentoo will either be a top-three distro again or everybody |
47 |
and their brother will be doing from-source distros and there will be as |
48 |
many of them as there are binary distros now. |
49 |
|
50 |
And of course what happens to a good portion of those presently flaky |
51 |
connections over another decade is just as up in the air. Ideally, it |
52 |
wouldn't be a problem we'd have to worry about by then, but I don't think |
53 |
anyone considers that likely. OTOH, it could be that more people are |
54 |
moving to mobile-only by then, and a /lower/ percentage of gentooers have |
55 |
reliable high-bandwidth connections that don't cost an arm and a leg per |
56 |
gigabyte. |
57 |
|
58 |
But regardless of why or how, I don't expect gentoo rsync syncing to have |
59 |
anything like the same level of usage, a decade from now. Maybe it'll |
60 |
still be around, with one or a half dozen gentoo rsync mirrors, but I |
61 |
don't expect there will be a need for the several per region that many |
62 |
regions have now. Of course I could be wrong, but I just don't see it. |
63 |
|
64 |
(And yes, I'm posting this in the full awareness that someone could |
65 |
dredge it from the archives a decade from now and point out how wrong I |
66 |
ended up being. In part that's why the "I could be wrong", to cover my |
67 |
bases, but I /still/ don't see it, and if it happens to be, my present |
68 |
self will be quite surprised, tho my future self might well find that in |
69 |
hindsight it should have been predictable, and I just didn't see it.) |
70 |
|
71 |
IOW, it's nothing individual users need to be concerned about in the near |
72 |
term (out to three years or so), /probably/ nothing they need to be |
73 |
concerned about in the intermediate term (say 3-6 years), and beyond |
74 |
that, so much is likely to have changed that any predictions made now are |
75 |
certain to have missed important events that drastically change the way |
76 |
we look at things in the mean time, and thus be rather off base. |
77 |
|
78 |
After all, git itself is only from 2005, 11 years ago, and ten years ago |
79 |
today, while it was definitely used for the kernel, I doubt that anyone |
80 |
would have predicted it would have pretty much taken over the (D)VCS |
81 |
landscape like it did, github and all. |
82 |
|
83 |
-- |
84 |
Duncan - List replies preferred. No HTML msgs. |
85 |
"Every nonfree program has a lord, a master -- |
86 |
and if you use the program, he is your master." Richard Stallman |