public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64]  Re: kdesdk-strigi-analyzer won't build
Date: Tue, 16 Sep 2008 23:06:42 +0000 (UTC)	[thread overview]
Message-ID: <pan.2008.09.16.23.06.41@cox.net> (raw)
In-Reply-To: 48CFD34D.2010204@ercbroadband.org

"Mark Haney" <mhaney@ercbroadband.org> posted
48CFD34D.2010204@ercbroadband.org, excerpted below, on  Tue, 16 Sep 2008
11:39:57 -0400:

> I didn't realize I had to explicitly deny the semantic-desktop use flag.

Not necessarily at you, specifically, but for the list in general...

That's why one should /always/ do an emerge --verbose --pretend (or --
ask, or the equivalent in your $PM) first.  Review the USE flags, 
checking to see if they're what you want and changing them if not.  This 
is particularly important for new packages.  After that, the color-coding 
helps you spot new/changed flags.  But note that even emerging an update 
to something may bring in different dependencies than the previous 
version did, so pay attention to the N/U indicator on dependencies as 
well, and examine the flags accordingly.

By following this advice since I first installed Gentoo back in 2004, I 
don't believe I've /ever/ been surprised by the status of a USE flag.  I 
/always/ check them (using --ask, normally) before I merge anything, use 
euse -i <flag> to find out what it is if necessary, and cancel out the 
merge and change it if I need to.

-- 
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




      parent reply	other threads:[~2008-09-16 23:06 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                       ` [gentoo-amd64] " Duncan
2008-09-16 23:06               ` Duncan [this message]

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.16.23.06.41@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