1 |
On Mon, 19 Sep 2011 10:43:04 -0400 |
2 |
Mike Frysinger <vapier@g.o> wrote: |
3 |
|
4 |
> On Monday, September 19, 2011 03:10:45 Michał Górny wrote: |
5 |
> > On Sun, 18 Sep 2011 18:39:32 -0400 Mike Frysinger wrote: |
6 |
> > > On Sunday, September 18, 2011 18:16:30 Nirbheek Chauhan wrote: |
7 |
> > > > On Mon, Sep 19, 2011 at 2:25 AM, Michał Górny wrote: |
8 |
> > > > > '$(use_enable static-libs static)' themselves. While at it, it |
9 |
> > > > > may be better to just drop the flag if no other package |
10 |
> > > > > relies on it and no user has ever requested the static build |
11 |
> > > > > of that package. |
12 |
> > > > |
13 |
> > > > I don't see any harm with including IUSE="static-libs" for every |
14 |
> > > > package that has working/usable static libraries[1]. Why wait |
15 |
> > > > for users to request it on bugzilla when it's a near-zero-cost |
16 |
> > > > and zero-maintenance to add it to ebuilds? |
17 |
> > > |
18 |
> > > i missed this sentence from Michał's e-mail. unconditionally not |
19 |
> > > building static libraries is against policy. if you install |
20 |
> > > shared libs that get linked against, then you must provide static |
21 |
> > > libraries unconditionally as well or support IUSE=static-libs. |
22 |
> > > maintainers do not get to choose "no one has asked for it and no |
23 |
> > > one in the tree is using it thus my ebuild isnt going to". |
24 |
> > |
25 |
> > Where is that policy? |
26 |
> |
27 |
> this policy predates much of the documentation process and is missed |
28 |
> by the developer handbook. it is however mentioned explicitly in the |
29 |
> devmanual. |
30 |
|
31 |
So, it a policy which even QA doesn't recall. It seems worth changing |
32 |
as there is really no reason to randomly install every possible static |
33 |
library out there if system does support and use shared linking. |
34 |
|
35 |
> > AFAIK the policy was to 'follow upstream' which |
36 |
> > usually means 'shared only'. I really don't see a reason to build |
37 |
> > static libtorrent as upstream even doesn't support static linking. |
38 |
> |
39 |
> by that token, i'll go ahead and remove glibc's static libraries |
40 |
> since upstream doesn't even support static linking |
41 |
|
42 |
I'm probably ignorant so you'd have to elaborate more on that to make |
43 |
me see a problem there. |
44 |
|
45 |
-- |
46 |
Best regards, |
47 |
Michał Górny |