1 |
Dnia 2014-03-02, o godz. 19:09:09 |
2 |
Jeroen Roovers <jer@g.o> napisał(a): |
3 |
|
4 |
> On Sun, 2 Mar 2014 12:32:05 -0500 |
5 |
> Mike Gilbert <floppym@g.o> wrote: |
6 |
> |
7 |
> > On Sun, Mar 2, 2014 at 10:45 AM, Jeroen Roovers <jer@g.o> |
8 |
> > wrote: |
9 |
> > > On Sun, 2 Mar 2014 09:37:22 +0100 |
10 |
> > > Michał Górny <mgorny@g.o> wrote: |
11 |
> > > |
12 |
> > >> Few months ago I have written a small FAQ on how to use slots |
13 |
> > >> and subslots for library dependencies properly [1]. However, today |
14 |
> > >> I see that most of the developers didn't care to properly update |
15 |
> > >> their packages and when I introduced binary compatibility slot in |
16 |
> > >> libgcrypt, I had my hands full of work fixing the mess for a |
17 |
> > >> single package. |
18 |
> > > |
19 |
> > > How about you file a tracker bug report for each library package, |
20 |
> > > and then file bug reports per package using that dependency |
21 |
> > > blocking the tracker bug? |
22 |
> > > |
23 |
> > |
24 |
> > That is certainly the conservative way to handle this, and it seems |
25 |
> > like a lot more work. |
26 |
> |
27 |
> Not managing the migration is apparently a lot of work, since the work |
28 |
> isn't being done "voluntarily". Managing the migration might seem like a |
29 |
> lot of work, but at least it allows you to track progress properly and |
30 |
> tick off finished tasks, while in the mean time everyone involved gets |
31 |
> informed, and perhaps gets their bugs fixed for them quicker. |
32 |
|
33 |
Except that with that number of bugs, some of them are going to get |
34 |
outdated very quickly due to version bumps where maintainer ignored |
35 |
the bug. |
36 |
|
37 |
And believe me, if I'll file around 50 bugs for each maintainer, they |
38 |
are not going to be happy. I guess some of them will be closed as |
39 |
DONTCARE, and others reassigned to me like I needed that. Pretty much |
40 |
like you keep assigning every bug with 'clang' in summary line to me |
41 |
like I was supposed to patch every package in the world for clang |
42 |
compatibility. |
43 |
|
44 |
> > If there are any reasonable objections (besides maintainer |
45 |
> > territorial-ism), of course the QA team should consider them. |
46 |
> |
47 |
> That's back to the "agreement" bit, I guess. |
48 |
> |
49 |
> Honestly, setting up a tracker and blocking it with bugs about packages |
50 |
> which someones-sub-SLOT-checking-script has vetted to be involved could |
51 |
> be done in less than a day (for the hundred or so packages that depend |
52 |
> on dev-libs/libgcrypt). It doesn't need some QA team to study in depth |
53 |
> -- it needs a couple of volunteers to do the checks and file the bug |
54 |
> reports. |
55 |
|
56 |
I'm not talking about libgcrypt. Those dependencies were 'mostly fixed' |
57 |
already and no sane person will revbump every single package just to |
58 |
make sure that everything will go right. Especially when Council |
59 |
banned a few EAPIs and the revbump would have to be connected with EAPI |
60 |
bump... and that would really make it all so happy and awesome. |
61 |
|
62 |
So I'm not talking about few dozen libgcrypt consumers. I'm talking |
63 |
about all packages in Gentoo that depend on at least a single library. |
64 |
I won't give you numbers but I guess you can imagine the number of |
65 |
bugs. |
66 |
|
67 |
-- |
68 |
Best regards, |
69 |
Michał Górny |