On 11/02/2013 14:09, Tanstaafl wrote: > On 2013-02-10 3:43 PM, Neil Bothwick <[email protected]> wrote: >> On Sun, 10 Feb 2013 15:40:00 -0500, Tanstaafl wrote: >> >>> Here's what IUSE says are enabled for the currently installed lvm2: >>> >>> readline +static +static-libs clvm cman +lvm1 selinux >> >> IUSE shows the flags that were available to that build, USE shows the >> flags that were used. > > Ah, thanks for that... > > Ok, so the current one was installed with:: > > amd64 elibc_glibc kernel_linux lvm1 multilib readline static static-libs > userland_GNU > > And the update wants to install with: > > USE="lvm1 readline thin%* udev%* (-clvm) (-cman) (-selinux) -static* > -static-libs*" > > So, what is with the differences? > > + thin udev > > Why is amd64, elibc_glibc, kernel_linux, multilib & userland_GNU not > included? > > and why omitting > > - static, static-libs > > ? > > Just trying to understand why the changes, and want to make sure lvm > isn't going to end up failing on me the next reboot... > > Thanks >
The answers to most of the questions you asked are in the ebuild file and in the ChangeLog. You can find them at $PORTDIR/sys-fs/lvm2/ amd64, elibc_glibc, kernel_linux, multilib & userland_GNU are not in emerge output as those are not USE flags in the regular sense of the word. Don't worry about them, they define the basic settings upon which portage built your host. Change any of them only at your peril, you will break things horribly (and keep N pieces, where N is a big number). You can see the full lot near the end of emerge --info -- Alan McKinnon [email protected]
