1 |
+1 for killing cvs |
2 |
|
3 |
|
4 |
Johannes Huber писал 2012-05-23 15:54: |
5 |
> Am Mittwoch 23 Mai 2012, 14:42:37 schrieb Michael Weber: |
6 |
> |
7 |
>> -----BEGIN PGP SIGNED MESSAGE----- |
8 |
> |
9 |
>> Hash: SHA256 |
10 |
> |
11 |
>> |
12 |
> |
13 |
>> Hi, |
14 |
> |
15 |
>> |
16 |
> |
17 |
>> i've looked at the blockers of "[TRACKER] portage migration to git" |
18 |
> |
19 |
>> [1] and want to discuss "testing git-cvsserver" [2]. |
20 |
> |
21 |
>> |
22 |
> |
23 |
>> There are two proposed scenarios how to migrate the developers write |
24 |
> |
25 |
> |
26 |
>> access to the portage tree. |
27 |
> |
28 |
>> |
29 |
> |
30 |
>> "Clean cut" turns of cvs access on a given and announced timestamp, |
31 |
> |
32 |
>> rsync-generation/updates is suspended (no input -> no changes), some |
33 |
> |
34 |
> |
35 |
>> magic scripts prepare the git repo (according to [3], some hours |
36 |
> |
37 |
>> duration) and we all checkout the tree (might be some funny massive |
38 |
> load). |
39 |
> |
40 |
>> |
41 |
> |
42 |
>> "testing git-cvsserver" proses "Clean cut" with the additional |
43 |
> ability |
44 |
> |
45 |
>> to continue using cvs update/commit, - in best case - on the old |
46 |
> |
47 |
>> checkout w/o alteration on the developers side. |
48 |
> |
49 |
>> |
50 |
> |
51 |
>> "Clean cut" forces us to clean up out dirty checkouts (I have some |
52 |
> |
53 |
>> added directories, added ebuilds i hesitated to `repoman commit`). |
54 |
> |
55 |
>> Plus we have to alter all our hot-wired portage mangling scripts |
56 |
> from |
57 |
> |
58 |
>> cvs'ish to git'ish (I use my read/write checkout as portage tree |
59 |
> (cvs |
60 |
> |
61 |
>> checkout + egencache for checkout) and have an automated |
62 |
> google-chrome |
63 |
> |
64 |
>> bump script). But this can be accomplished on a per developer basis, |
65 |
> |
66 |
> |
67 |
>> and slackers don't stall the process. |
68 |
> |
69 |
>> |
70 |
> |
71 |
>> "testing git-cvsserver" forces us all to test these cvs'ish scripts |
72 |
> |
73 |
>> and behaviours against a git-cvsserver and report. |
74 |
> |
75 |
>> We all know that this test-runs will never happen, stalling this bug |
76 |
> |
77 |
> |
78 |
>> till infinity. |
79 |
> |
80 |
>> Plus infra/"subset of devs marshalling the migration" get stuck |
81 |
> |
82 |
>> between fixing git issues and git-cvsserver. |
83 |
> |
84 |
>> |
85 |
> |
86 |
>> *if you still read this* *wow* |
87 |
> |
88 |
>> |
89 |
> |
90 |
>> Please discuss my arguments and come to the conclusions to |
91 |
> |
92 |
>> RESO/WONT-FIX "testing git-cvsserver", make a "clean cut" and remove |
93 |
> |
94 |
> |
95 |
>> this bug from the blockers of "[TRACKER] portage migration to git". |
96 |
> |
97 |
>> |
98 |
> |
99 |
>> My lengthy 2 cents. |
100 |
> |
101 |
>> |
102 |
> |
103 |
>> [1] https://bugs.gentoo.org/333531 |
104 |
> |
105 |
>> [2] https://bugs.gentoo.org/333699 |
106 |
> |
107 |
>> [3] https://bugs.gentoo.org/333705#c2 |
108 |
> |
109 |
>> - -- |
110 |
> |
111 |
>> Gentoo Dev |
112 |
> |
113 |
>> http://xmw.de/ |
114 |
> |
115 |
>> -----BEGIN PGP SIGNATURE----- |
116 |
> |
117 |
>> Version: GnuPG v2.0.17 (GNU/Linux) |
118 |
> |
119 |
>> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
120 |
> |
121 |
>> |
122 |
> |
123 |
>> iF4EAREIAAYFAk+82z0ACgkQknrdDGLu8JBUWAD/dmuqyES/mYDrMam+/txnHmgd |
124 |
> |
125 |
>> VaQaqwHMlwzzqQwbpY4A/0h+5Vp8sLbOE78k4SCaGE2dCQtmeOz0jd1YxkDzP+YW |
126 |
> |
127 |
>> =jXLQ |
128 |
> |
129 |
>> -----END PGP SIGNATURE----- |
130 |
> |
131 |
> I support RESOLUTION WONTFIX, if nobody cares about the bug since it |
132 |
> was opened it is obvious out of interest. There is no reason to |
133 |
> support jurassic software. |
134 |
> |
135 |
> Clean cut++ |
136 |
> |
137 |
> Cheers |
138 |
|
139 |
-- |
140 |
Best Regards, |
141 |
Alexey 'Alexxy' Shvetsov |
142 |
Petersburg Nuclear Physics Institute, NRC Kurchatov Institute, |
143 |
Gatchina, Russia |
144 |
Department of Molecular and Radiation Biophysics |
145 |
Gentoo Team Ru |
146 |
Gentoo Linux Dev |
147 |
mailto:alexxyum@×××××.com |
148 |
mailto:alexxy@g.o |
149 |
mailto:alexxy@×××××××××××××.ru |