1 |
On 24 June 2012 21:56, Michael Palimaka <kensington@g.o> wrote: |
2 |
> On 2012-06-24 18:34, Ben de Groot wrote: |
3 |
>> |
4 |
>> We at qt@ have been discussing this on and off. We would like to |
5 |
>> see a linguas.eclass happen, because already now we start having |
6 |
>> code duplication. So instead of this duplication of code between |
7 |
>> qt4-r2 and cmake-utils eclasses, why not put this into a separate |
8 |
>> linguas.eclass that both can inherit? |
9 |
|
10 |
Actually, I was just thinking, since we are talking about two variables |
11 |
and a few lines of code, maybe it would be better to add this to |
12 |
base.eclass? |
13 |
|
14 |
>> Obviously the problem with handling more than just setting IUSE |
15 |
>> is the variety of ways in which linguas are handled by different |
16 |
>> packages and different build systems. |
17 |
> |
18 |
> I agree that linguas.eclass is a good idea, but how possible is it to |
19 |
> incorporate the various build systems, and the various approaches used by |
20 |
> each package? |
21 |
> |
22 |
> If you have some ideas, I'm more than happy to help. |
23 |
|
24 |
We could look at the most common use cases, and see if we can |
25 |
come up with something generic that would work for most of |
26 |
those. |
27 |
|
28 |
We have some code in the qt overlay, but that is obviously |
29 |
Qt specific. |
30 |
|
31 |
-- |
32 |
Cheers, |
33 |
|
34 |
Ben | yngwin |
35 |
Gentoo developer |
36 |
Gentoo Qt project lead |