public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: meino.cramer@gmx.de
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Checking the reason for (-useflags) in brackets
Date: Sat, 21 Jun 2014 12:58:17 +0200	[thread overview]
Message-ID: <20140621105817.GC3899@solfire> (raw)
In-Reply-To: <53A55F02.5010101@gmail.com>

Alan McKinnon <alan.mckinnon@gmail.com> [14-06-21 12:36]:
> On 21/06/2014 11:19, meino.cramer@gmx.de wrote:
> > Hi,
> > 
> > for some applications I want to activate some USE flags, which are
> > disabled by default.
> > 
> > Some of those USE flags are set in () brackets. From searching the
> > internet I learned, that this may be due to unresolveable dependencies
> > or settings in the make.profile or....
> > 
> > Is there a way to exactly pin point the reason why a certain USE flags
> > gets "(diabled)" and whether it is possible to resolve the problem?
> > 
> > How can I figure out that?
> 
> 
> From the emerge man page:
> 
> 
>  ()       circumfix   forced, masked, or removed
> 
> 
> So the answer is usually one of
> 
> - flag not in ebuild anymore. Look in the ebuild
> - masked in profile. For these I usually search the profile directory
> recursively for the flag and figure it out that way
> 
> 
> What is it that you are trying to find out? A disabled flag is disabled
> and can't work, what further detail do you need?
> 
> 
> 
> -- 
> Alan McKinnon
> alan.mckinnon@gmail.com
> 
> 

Thanks for your help. In the internet I have already found the answer
in the meanwhile.


Best regards,
mcc



  reply	other threads:[~2014-06-21 10:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-21  9:19 [gentoo-user] Checking the reason for (-useflags) in brackets meino.cramer
2014-06-21 10:31 ` Alan McKinnon
2014-06-21 10:58   ` meino.cramer [this message]
2014-06-21 11:58     ` [gentoo-user] " Jörg Schaible

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=20140621105817.GC3899@solfire \
    --to=meino.cramer@gmx.de \
    --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