in the output of equery uses lvm2, the description of static is not correct because it need to be defined in the metadata.xml Reproducible: Always Steps to Reproduce: 1.equery uses lvm2 Actual Results: gentoo-test lvm2 # equery uses lvm2 [ Legend : U - final flag setting for installation] [ : I - package is installed with flag ] [ Colors : set, unset ] * Found these USE flags for sys-fs/lvm2-2.02.97-r1: U I + + lvm1 : Allow users to build lvm2 with lvm1 support + + readline : Enables support for libreadline, a GNU line-editing library that almost everyone wants + + static : !!do not set this during bootstrap!! Causes binaries to be statically linked instead of dynamically - - static-libs : Build static libraries + + thin : Support for thin volumes + + udev : Enable sys-fs/udev integration (device discovery, power and storage device support, etc) Expected Results: gentoo-test lvm2 # equery uses lvm2 [ Legend : U - final flag setting for installation] [ : I - package is installed with flag ] [ Colors : set, unset ] * Found these USE flags for sys-fs/lvm2-2.02.97-r1: U I + + lvm1 : Allow users to build lvm2 with lvm1 support + + readline : Enables support for libreadline, a GNU line-editing library that almost everyone wants + + static : Building static LVM, for usage inside genkernel - - static-libs : Build static libraries + + thin : Support for thin volumes + + udev : Enable sys-fs/udev integration (device discovery, power and storage device support, etc) --- metadata.xml.orig 2013-04-25 21:41:22.000000000 +0900 +++ metadata.xml 2013-04-25 21:40:21.000000000 +0900 @@ -19,5 +19,6 @@ <flag name='cman'>Cman support for clustered lvm</flag> <flag name='lvm1'>Allow users to build lvm2 with lvm1 support</flag> <flag name='thin'>Support for thin volumes</flag> + <flag name='static'>Building static LVM, for usage inside genkernel</flag> </use> </pkgmetadata>
I changed the Summary because there is nothing "wrong" with the current description - with USE=static, you get statically linked binaries. This may be useful particularly for use in an initramfs, but it isn't exclusive.
Created attachment 346580 [details, diff] add static flag name
(In reply to comment #2) > Created attachment 346580 [details, diff] [details, diff] > add static flag name The current description is better. "Causes binaries to be statically linked instead of dynamically" which is exactly what happens. It's not related to genkernel specifically at all.
genkernel no longer needs static, so no change is needed
