1 |
On Thu, Mar 8, 2018 at 10:40 AM, Michał Górny <mgorny@g.o> wrote: |
2 |
> |
3 |
> So, developers, please *stop adding USE=static-libs* to random libraries |
4 |
> that have no reason whatever to be statically linked to. And by that I |
5 |
> mean a good reason, not creeping featurism, not 'user asked for it', not |
6 |
> 'this broken package hardcodes libfoo.a'. |
7 |
> |
8 |
|
9 |
While I agree with all the arguments against using static libs, this |
10 |
seems a bit contrary to the spirit of Gentoo. Certainly building |
11 |
static libs shouldn't be the default. However, if for some reason a |
12 |
user feels they need static libs, do we really need to make them jump |
13 |
through a million hoops simply because maybe we wouldn't do the same |
14 |
thing in their shoes? |
15 |
|
16 |
Why not just let maintainers add support if they wish, and neither |
17 |
require them to do so nor prohibit or discourage them? |
18 |
|
19 |
Now, if a package requires static linking that should be considered a |
20 |
bug, except where it really does make sense (bootloaders, kernels, |
21 |
firmware, etc). If a package installs static libs by default this |
22 |
should generally also be a bug. |
23 |
|
24 |
IMO this is not a feature that causes harm simply by being available. |
25 |
It isn't like a dialog box that has 500 boxes to hunt through. This |
26 |
is a global use flag that everybody understands, and which defaults to |
27 |
off. Keep in mind also that a lot of people use Gentoo in weird |
28 |
niches, and flexibility is our main selling point. Our users |
29 |
shouldn't have to beg to have use cases supported if it is easy to |
30 |
support them, just because their use cases are rare. If we excluded |
31 |
all rare use cases from Gentoo we'd probably exclude just about all of |
32 |
them in practice, because if somebody just wanted Ubuntu or CentOS or |
33 |
Debian they'd be using Ubuntu or CentOS or Debian. |
34 |
|
35 |
Just my own two cents here. |
36 |
|
37 |
-- |
38 |
Rich |