1 |
On 3 October 2010 15:29, Luca Barbato <lu_zero@g.o> wrote: |
2 |
> I think the simpler solution is that if it needs .la, before reaching the |
3 |
> tree it has to be fixed... |
4 |
|
5 |
What I'm not keen about that is that using the .la files isn't really |
6 |
"broken" - if libfoo uses libtool, and some other software uses |
7 |
libfoo's .la files in a way that works with the upstream version of |
8 |
libfoo, then it ought to work with Gentoo's libfoo too. (This gets |
9 |
into arguments about what sorts of changes are appropriate for a |
10 |
distribution to make, versus being left to upstream.) |
11 |
|
12 |
Also, not every piece of software that people might want to use is |
13 |
going to go into the main tree - people can use Gentoo to develop |
14 |
their own software (and might have their own ideas (or their |
15 |
company/project's ideas) about what parts of libtool it's appropriate |
16 |
to rely on), use packages from overlays, compile other people's |
17 |
software outside the package management system, run precompiled |
18 |
binaries, etc. Again, from here I'm sure you can have a big |
19 |
discussion about whether libraries in the tree exist only to support |
20 |
applications in the tree, or whether they're "products" (for want of a |
21 |
better word) in their own right. |
22 |
|
23 |
Again, maybe not earth-shatteringly important issues, but I do think |
24 |
these should at least be considered when deciding the policy. |