-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 06/08/13 04:17 PM, Ian Stakenvicius wrote: > On 30/07/13 04:42 AM, Samuli Suominen wrote: > >> 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 - RESO/TEST - >> cryptsetup static+pcre fails (fixed via resolution of bug >> 439414) > >> https://bugs.gentoo.org/show_bug.cgi?id=468400 - RESO/TEST - >> cryptsetup static+selinux fails (fixed via resolution of bug >> 439414) > >> https://bugs.gentoo.org/show_bug.cgi?id=472692 - RESO/FIXED - >> cryptsetup static+ssl fails (note, only cryptsetup-1.6.1 fixed, >> so this should get pushed stable) > >> https://bugs.gentoo.org/show_bug.cgi?id=462908 - RESO/FIXED - >> 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 - RESO/FIXED - >> 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 - RESO/FIXED - >> lvm2 static+selinux fails > > > So dropping IUSE="static" becomes a no-op now, right? >
It should also be noted that these bugs really boiled down to 2-3 changes that were quite trivial to fix. It is quite unfortunate that nobody had put the time in to figure them out and fix them, though. IUSE="static" support is really not that broken, but we certainly need to step up in addressing bugs like these (and others) instead of letting them sit and fester for months. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.20 (GNU/Linux) iF4EAREIAAYFAlIBXZkACgkQ2ugaI38ACPBelAD+OLi+EC2pjfe2wGNkvbIL96YG U3BmlMxHTj8OYKHUNXkBAJoHlriZmdTFClf0RYNpll1206rt0fnl9dl0gc7XUukS =0bEa -----END PGP SIGNATURE-----
