| 1 |
On Wed, Sep 14, 2011 at 16:03, Michał Górny wrote: |
| 2 |
> Well, the other thing is IUSE=static-libs. I don't like it either but |
| 3 |
> this is probably a bigger case than the other. |
| 4 |
> |
| 5 |
> The main resolution as I see it, is to simply drop IUSE=static-libs |
| 6 |
> from a lot of ebuilds where static libs aren't actually required by |
| 7 |
> anything or anyone. |
| 8 |
|
| 9 |
no ... the current policy (and i see no reason to change it) is: |
| 10 |
- always build shared and static libs |
| 11 |
- always build shared libs and control static libs via USE=static-libs |
| 12 |
|
| 13 |
so if the library can be statically linked against, the ebuild needs |
| 14 |
to support it. a valid test is not "does any other package in the |
| 15 |
tree want to link against this", nor is "i dont want static libs, and |
| 16 |
i cant find anyone who does". most people dont want to do static |
| 17 |
linking most of the time, but that number is not 0. |
| 18 |
-mike |
Archives