1 |
On 2 October 2010 20:54, Jorge Manuel B. S. Vicetto |
2 |
<jmbsvicetto@g.o> wrote: |
3 |
> Given the recent activity around .la files and conflict about how to |
4 |
> deal with them, I propose we discuss this issue in this mailing list, |
5 |
> and take this issue to the council. |
6 |
> That way, we can make a global decision, taking into account all the |
7 |
> arguments for and against, find a balance, opt for a policy, inform |
8 |
> users and developers about it and move on. |
9 |
|
10 |
While I do agree that the underlying problem we're trying to solve is |
11 |
worth solving, I do have a couple of small concerns about how it's |
12 |
being done. The first is that it seems people are judging whether a |
13 |
particular .la file is "needed" by checking whether anything currently |
14 |
in the tree needs it, but this doesn't take into account anything that |
15 |
/isn't/ in the tree yet. The second is that removing .la files |
16 |
everywhere makes it hard for people to experiment with alternative |
17 |
solutions, as testing an alternative would require modifying all the |
18 |
affected ebuilds to stop removing them. (And yes, I am interested in |
19 |
doing so myself, although time constraints mean it might not |
20 |
happening.) |
21 |
|
22 |
Would it be too much trouble to have a standardised variable that |
23 |
means .la files should be kept? It maybe /shouldn't/ be exposed as a |
24 |
USE flag because very few people will need it, but if it's easy to |
25 |
implement (maybe by having an eutils function to do the removal, |
26 |
checking the variable first) it would remove any objections I could |
27 |
imagine. |
28 |
|
29 |
As I said, these are minor points, and I wouldn't expect people to go |
30 |
to great effort to satisfy them. Just something to consider. |