From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: kdesdk-strigi-analyzer won't build
Date: Wed, 17 Sep 2008 21:12:23 +0000 (UTC) [thread overview]
Message-ID: <pan.2008.09.17.21.12.22@cox.net> (raw)
In-Reply-To: 48D11718.9030300@ercbroadband.org
"Mark Haney" <mhaney@ercbroadband.org> posted
48D11718.9030300@ercbroadband.org, excerpted below, on Wed, 17 Sep 2008
10:41:28 -0400:
> I just emerged the new kdelibs but when I did an 'equery hasuse
> semantic-desktop' this is what I got:
>
> [ Searching for USE flag semantic-desktop in all categories among: ]
> * installed packages
> [I--] [ ~] kde-base/kdelibs-4.0.5 (kde-4) [I--] [ ~]
> kde-base/dolphin-4.0.5 (kde-4) [I--] [ ~] kde-base/kdelibs-4.1.1 (4.1)
> [I--] [M~] kde-base/gwenview-4.1.0 (4.1) [I--] [M~]
> kde-base/dolphin-4.1.0 (4.1) [I--] [M~] kde-base/kget-4.1.0 (4.1)
>
> But, kdelibs-4.1.1 was just emerged without that use flag. I don't
> understand what's going on. I've checked using equery hasuse on strigi,
> nepomuk and semantic-desktop and the only one that shows any output is
> the one above.
I've not merged KDE4 since I decided it wasn't ready a few months ago, so
won't touch that, however...
equery hasuse <flag> lists all packages that have that USE flag, whether
it is turned on or not. To see if a flag is actually turned on for an
individual package, use equery uses <package>, or to see what it /will/
be merging with, use emerge --pretend --verbose.
So use equery hasuse to get a list of packages that have that use flag,
then check them individually to see if it's turned on.
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2008-09-17 21:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 13:18 [gentoo-amd64] kdesdk-strigi-analyzer won't build Mark Haney
2008-09-16 13:57 ` Beso
2008-09-16 14:04 ` Mark Haney
2008-09-16 14:17 ` Beso
2008-09-16 14:17 ` cuciferus
2008-09-16 14:19 ` Beso
2008-09-16 14:21 ` Mark Haney
2008-09-16 14:27 ` Beso
2008-09-16 15:12 ` Mark Haney
2008-09-16 15:31 ` Beso
2008-09-16 15:39 ` Mark Haney
2008-09-16 15:46 ` Beso
2008-09-16 17:53 ` Mark Haney
2008-09-16 18:44 ` Beso
2008-09-17 14:41 ` Mark Haney
2008-09-17 15:09 ` Beso
2008-09-17 15:17 ` Mark Haney
2008-09-17 16:03 ` Jan Jitse Venselaar
2008-09-17 16:05 ` Mark Haney
2008-09-17 16:45 ` Jan Jitse Venselaar
2008-09-17 19:14 ` Beso
2008-09-17 19:54 ` Mark Haney
2008-09-17 20:10 ` Beso
2008-09-17 21:12 ` Duncan [this message]
2008-09-16 23:06 ` [gentoo-amd64] " Duncan
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=pan.2008.09.17.21.12.22@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-amd64@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