1 |
Hello, everybody. |
2 |
|
3 |
On Sat, Nov 29, 2014 at 07:09:07AM +0000, Martin Vaeth wrote: |
4 |
> hasufell <hasufell@g.o> wrote: |
5 |
> > Martin Vaeth: |
6 |
> >> hasufell <hasufell@g.o> wrote: |
7 |
> >>>> With rsync I believe you can exclude categories: |
8 |
> >>>> http://www.gentoo-wiki.info/TIP_Exclude_categories_from_emerge_sync |
9 |
|
10 |
> >>> That is uninformed. |
11 |
|
12 |
> >> I think he is right. |
13 |
|
14 |
> >>> check the --depth option of git. You can even clone specific tags with |
15 |
> >>> --depth=1. |
16 |
|
17 |
> >> Every tag will still contain all categories: |
18 |
> >> AFAIK, with git, it is not possible to update everyting but e.g. *access* |
19 |
> >> *kde* *i10n* *gnome* if you know that you will never install an |
20 |
> >> ebuild from these categories. |
21 |
|
22 |
> > My max DL rate is ~700KiB/s and is the limiting factor. |
23 |
|
24 |
> My concern is not the time but the total volume (there are still |
25 |
> often limitations involved), and perhaps even more important, |
26 |
> the disk usage, especially compared with methods like squashfs(+aufs). |
27 |
> It simply is a fact that with git you have to download and store a |
28 |
> lot of unnecessary information (if you are not a developer and do |
29 |
> not use a heavy system): not only git metadata but also |
30 |
> unneeded categories. |
31 |
> So for non-developers, downloading with git does not necessarily |
32 |
> make sense. |
33 |
|
34 |
> That being said, please do not consider this as an argument against |
35 |
> a change to git: For developers it has only advantages, and AFAIK, |
36 |
> it is not planned to cancel other download methods anyway. |
37 |
|
38 |
Speaking as a developer in a project which has just converted to git, I |
39 |
can assure you that git has tremendous disadvantages, even compared with |
40 |
cvs. |
41 |
|
42 |
Principally, git does not have a high level model of version control |
43 |
concepts, so that using git is somewhat analogous to programming in |
44 |
assembler. Both give you tremendous control and the ability to do |
45 |
practically anything, including shooting yourself in the foot. So that |
46 |
instead of conceptualising a "branch" (as you would do with Mercurial, |
47 |
Bazaar, Subversion, or even CVS), you need to think about "commits |
48 |
reachable from a certain head (excluding commits reachable from some |
49 |
other head)". |
50 |
|
51 |
git is very difficult to learn, compared with, say Mercurial. To |
52 |
compare, if you do $ git help branch, you get a man page ~180 lines long |
53 |
dumped on you, and that's taking up the full width of my 240 character |
54 |
wide screen. If you do $ hg help branch, you get a 27 line concise |
55 |
summary, max. ~80 characters wide, which nonetheless is pretty much |
56 |
complete. |
57 |
|
58 |
git has become very popular (much as systemd has), possibly because |
59 |
programmers are frustrated at not being able to write in assembler any |
60 |
more. (At least, that's my theory). Like systemd, it has established a |
61 |
stranglehold on its domain. But severe disadvantages it most definitely |
62 |
has. |
63 |
|
64 |
-- |
65 |
Alan Mackenzie (Nuremberg, Germany). |