| 1 |
On 27/08/2012 17:15, hasufell wrote: |
| 2 |
> Is there a reason not to support static-libs in an ebuild if the package |
| 3 |
> supports it? |
| 4 |
|
| 5 |
Most libtool software "supports" static-libs, because libtool let you |
| 6 |
build them, _but_ it might not be test or might not even work. |
| 7 |
|
| 8 |
One example is software that relies on plug-ins, such as xine-lib. or |
| 9 |
stuff that links to gmodule. Having static libraries there is |
| 10 |
technically possible, but if you do you have a bag full of problems and |
| 11 |
nothing else. |
| 12 |
|
| 13 |
> It seems some developers don't care about this option. What's the gentoo |
| 14 |
> policy on this? Isn't this actually a bug? |
| 15 |
|
| 16 |
I honestly don't usually put static-libs "just because" — if a case can |
| 17 |
be made about static libs to be useful, I'm always open to add an USE |
| 18 |
flag, but "because I can" is not an option for me. |
| 19 |
|
| 20 |
-- |
| 21 |
Diego Elio Pettenò — Flameeyes |
| 22 |
flameeyes@×××××××××.eu — http://blog.flameeyes.eu/ |
Archives