1 |
El mar, 30-07-2013 a las 11:42 +0300, Samuli Suominen escribió: |
2 |
> On 29/07/13 23:57, Pacho Ramos wrote: |
3 |
> > Hello |
4 |
> > |
5 |
> > As discussed at: |
6 |
> > https://bugs.gentoo.org/show_bug.cgi?id=478476 |
7 |
> > |
8 |
> > Upstream is dropping static libs from udev and, then, sys-apps/udev is |
9 |
> > currently reverting that commit downstream (even if upstream says some |
10 |
> > problems could appear in the future as nobody is taking care of static |
11 |
> > stuff there). |
12 |
> > |
13 |
> > Grepping in the tree, looks like only some old genkernel versions are |
14 |
> > depending on it. Apart of that, what is requiring static libs in |
15 |
> > cryptsetup and lvm2? |
16 |
> > |
17 |
> > Thanks a lot |
18 |
> > |
19 |
> |
20 |
> cryptsetup upstream installed minimal Gentoo setup and tested our |
21 |
> handling of 'static' and was disappointed finding them broken |
22 |
> |
23 |
> https://bugs.gentoo.org/show_bug.cgi?id=438998 - cryptsetup static+pcre |
24 |
> fails |
25 |
> |
26 |
> https://bugs.gentoo.org/show_bug.cgi?id=468400 - cryptsetup |
27 |
> static+selinux fails |
28 |
> |
29 |
> https://bugs.gentoo.org/show_bug.cgi?id=472692 - cryptsetup static+ssl fails |
30 |
> |
31 |
> https://bugs.gentoo.org/show_bug.cgi?id=462908 - lvm2 static-libs |
32 |
> missing library |
33 |
> |
34 |
> https://bugs.gentoo.org/show_bug.cgi?id=467204 - lvm2 static USE flag |
35 |
> missing proper description, yes this is minor |
36 |
> |
37 |
> https://bugs.gentoo.org/show_bug.cgi?id=370217 - lvm2 fails to build due |
38 |
> to missing -lrt, likely related to linking against libudev, yes the |
39 |
> feature we are discussing to be dropped has been completely broken for ages |
40 |
> |
41 |
> https://bugs.gentoo.org/show_bug.cgi?id=439414 - lvm2 static+selinux fails |
42 |
> |
43 |
> So we are not talking about removing anything that works, but something |
44 |
> users get hit by reading outdated guides that instruct them to enable |
45 |
> USE=static |
46 |
> |
47 |
> +1 for punting broken features |
48 |
> |
49 |
> |
50 |
|
51 |
We should drop that broken support I guess, but will CC its maintainers |
52 |
here too (they are CCed in bug report already) |