1 |
On Sat, 2007-12-08 at 15:49 +0200, Alon Bar-Lev wrote: |
2 |
> |
3 |
> gnupg-2 is drop-in replacement of gnupg-1, so eventually no slotting |
4 |
> should be used. |
5 |
|
6 |
Drop in according to YOU, which I have taken issue with since 1/1/07. |
7 |
|
8 |
Per last upstream release, and every one since 2.x was release, just as |
9 |
I have quoted and stated many times before. |
10 |
|
11 |
http://lists.gnupg.org/pipermail/gnupg-announce/2007q3/000259.html |
12 |
|
13 |
"GnuPG-2 has a different architecture than GnuPG-1 (e.g. 1.4.6) in that |
14 |
it splits up functionality into several modules. However, both |
15 |
versions may be installed alongside without any conflict. In fact, |
16 |
the gpg version from GnuPG-1 is able to make use of the gpg-agent as |
17 |
included in GnuPG-2 and allows for seamless passphrase caching. The |
18 |
advantage of GnuPG-1 is its smaller size and the lack of dependency on |
19 |
other modules at run and build time. We will keep maintaining GnuPG-1 |
20 |
versions because they are very useful for small systems and for server |
21 |
based applications requiring only OpenPGP support." |
22 |
|
23 |
> As far as I see, there are two migration pathes I can use: |
24 |
|
25 |
There is a third you have refused for almost a year now. |
26 |
|
27 |
1.x should remain slot 0, 2.x should be slot 2. |
28 |
|
29 |
http://bugs.gentoo.org/show_bug.cgi?id=159623 |
30 |
|
31 |
I also mentioned that if left unaddressed I would challenge this issue |
32 |
when it came time for stabilization. Which gnupg2 was release over a |
33 |
year ago now. Main reason that held it back so long was refusal to slot |
34 |
2.x versions, in any slot other than 0. Just as 1.9 was slotted. |
35 |
|
36 |
Even if all technical issues with gnupg 2.x have been worked out. It is |
37 |
NOT a drop in replacement for 1.x. The two are different and DESIGNED to |
38 |
work together. We will effectively rob users of the choice of 1.x for |
39 |
what ever reasons and force 2.x on them. Which deviates from all other |
40 |
distros. |
41 |
|
42 |
Not to mention we symlink gpg -> gpg2, and gpg2 does not implement all |
43 |
features of gpg, command line args. By default upstream spits out the |
44 |
binaries on build with different names, same thing with .so's and etc. |
45 |
So there isn't any conflict/collision problems. In fact just the |
46 |
opposite if one hits gpg expecting a gpg command feature set, and |
47 |
instead getting a gpg2 one. |
48 |
|
49 |
I have wasted weeks on this posting on comments on bugs. Brought up the |
50 |
issue here before. We have lost a year wrt to gnupg 2. I am all for |
51 |
moving forward and dropping legacy versions of packages from the tree. |
52 |
But this is not one IMHO. |
53 |
|
54 |
Last post on this topic, ever for me. It's WAY stupid at this point. The |
55 |
horse has been beaten to death, exhumed, killed again, re-exhumed, |
56 |
mummified, put on exhibit, taken down, killed again, and re-buried :) |
57 |
|
58 |
-- |
59 |
William L. Thomson Jr. |
60 |
Gentoo/Java |