[gentoo-dev] Re: Dropping static libs support from cryptsetup and lvm2

[Samuli Suominen]

On 29/07/13 23:57, Pacho Ramos wrote:
> Hello
>
> As discussed at:
> https://bugs.gentoo.org/show_bug.cgi?id=478476
>
> Upstream is dropping static libs from udev and, then, sys-apps/udev is
> currently reverting that commit downstream (even if upstream says some
> problems could appear in the future as nobody is taking care of static
> stuff there).
>
> Grepping in the tree, looks like only some old genkernel versions are
> depending on it. Apart of that, what is requiring static libs in
> cryptsetup and lvm2?
>
> Thanks a lot
>

cryptsetup upstream installed minimal Gentoo setup and tested our 
handling of 'static' and was disappointed finding them broken

https://bugs.gentoo.org/show_bug.cgi?id=438998 - cryptsetup static+pcre 
fails

https://bugs.gentoo.org/show_bug.cgi?id=468400 - cryptsetup 
static+selinux fails

https://bugs.gentoo.org/show_bug.cgi?id=472692 - cryptsetup static+ssl fails

https://bugs.gentoo.org/show_bug.cgi?id=462908 - lvm2 static-libs 
missing library

https://bugs.gentoo.org/show_bug.cgi?id=467204 - lvm2 static USE flag 
missing proper description, yes this is minor

https://bugs.gentoo.org/show_bug.cgi?id=370217 - lvm2 fails to build due 
to missing -lrt, likely related to linking against libudev, yes the 
feature we are discussing to be dropped has been completely broken for ages

https://bugs.gentoo.org/show_bug.cgi?id=439414 - lvm2 static+selinux fails

So we are not talking about removing anything that works, but something 
users get hit by reading outdated guides that instruct them to enable 
USE=static

+1 for punting broken features