public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Tanstaafl <tanstaafl@libertytrek.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] New USE flags for lvm2?
Date: Mon, 11 Feb 2013 07:09:48 -0500	[thread overview]
Message-ID: <5118DF8C.2000703@libertytrek.org> (raw)
In-Reply-To: <20130210204335.1201a838@digimed.co.uk>

On 2013-02-10 3:43 PM, Neil Bothwick <neil@digimed.co.uk> 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


  reply	other threads:[~2013-02-11 12:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-10 18:37 [gentoo-user] New USE flags for lvm2? Tanstaafl
2013-02-10 18:47 ` Florian Philipp
2013-02-10 19:07   ` Tanstaafl
2013-02-10 19:39     ` Florian Philipp
2013-02-10 19:57     ` Neil Bothwick
2013-02-10 20:40       ` Tanstaafl
2013-02-10 20:43         ` Neil Bothwick
2013-02-11 12:09           ` Tanstaafl [this message]
2013-02-11 15:15             ` Alan McKinnon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5118DF8C.2000703@libertytrek.org \
    --to=tanstaafl@libertytrek.org \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox