1 |
On Wed, 2019-05-08 at 12:19 +0200, Alexis Ballier wrote: |
2 |
> On Wed, 08 May 2019 12:01:21 +0200 |
3 |
> Michał Górny <mgorny@g.o> wrote: |
4 |
> |
5 |
> > On Wed, 2019-05-08 at 11:54 +0200, Alexis Ballier wrote: |
6 |
> > > On Wed, 08 May 2019 11:41:41 +0200 |
7 |
> > > Michał Górny <mgorny@g.o> wrote: |
8 |
> > > |
9 |
> > > > > There's multilib that adds a lot of flags with a single eclass |
10 |
> > > > > change, but I'd guess the number of packages and flags is |
11 |
> > > > > constantly growing, so sooner or later you'll be hit by this |
12 |
> > > > > again and no multilib killing will help you then. |
13 |
> > > > > |
14 |
> > > > > I think it is more future proof to use the addition of multilib |
15 |
> > > > > flags to fix pkgcheck rather than actively reducing the number |
16 |
> > > > > of multilib flags to cope with its limitations. |
17 |
> > > > |
18 |
> > > > Then please do it, by all means. The reality is simple. If the |
19 |
> > > > tool is broken, you either fix it or stop doing what you know |
20 |
> > > > that breaks it. Being unable to do the former, and having no good |
21 |
> > > > replacement, I'd go for the latter. |
22 |
> > > |
23 |
> > > Well, why is it slow ? IO ? CPU ? Did you collect profiling data ? |
24 |
> > |
25 |
> > CPU definitely. More detail than that, I don't and I don't have time |
26 |
> > to investigate. |
27 |
> |
28 |
> So you don't have time to change 3 lines to add cProfile but do have |
29 |
> time to send various emails and rework the entire multilib system ? |
30 |
> weird. |
31 |
|
32 |
Instead of being so smug, you could have provided helpful instructions |
33 |
on how to do it. Or did it yourself. |
34 |
|
35 |
Removing unused flags from multilib-build.eclass is certainly less work |
36 |
than that. |
37 |
|
38 |
|
39 |
-- |
40 |
Best regards, |
41 |
Michał Górny |