From: Alec Ten Harmsel <alec@alectenharmsel.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: cups-filters failing to build
Date: Mon, 24 Nov 2014 21:04:57 -0500 [thread overview]
Message-ID: <5473E3C9.9050202@alectenharmsel.com> (raw)
In-Reply-To: <5473DCDE.8040006@wraeth.id.au>
On 11/24/2014 08:35 PM, wraeth wrote:
> On 25/11/14 12:26, walt wrote:
> > A question of my own: the ebuilds for icedtea list the cups flag
> > as +cups. So far I haven't discovered a man page that explains the
> > + prefix. Is there such a man page?
>
> I just had a look through the man pages of emerge, portage and ebuild,
> plus at the Gentoo Devmanual and couldn't find anything; however I'm
> reasonably certain that in the context of an ebuild, a use flag
> defined as "+flag" means that it is defaulted to enabled by the ebuild.
>
Yes, this is correct.
> Running emerge with the -d flag can sometimes shed some light. More light than
> you probably want
I'll get right on this. Didn't know about (or forgot about) -d.
> I see there is a cups USEFLAG for icedtea. Could you unset that flag for
> icedtea as a workaround?
icedtea is weird - according to equery, +cups makes cups a build-time
only dependency, instead a build *and* runtime dependency.
Also, I just installed with and without '-d', and it now works. So I
guess this has been solved, but it's still strange. It might be that I
installed just cups-filters with --oneshot, but who knows.
Alec
next prev parent reply other threads:[~2014-11-25 2:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 22:24 [gentoo-user] cups-filters failing to build Alec Ten Harmsel
2014-11-25 1:26 ` [gentoo-user] " walt
2014-11-25 1:35 ` wraeth
2014-11-25 2:04 ` Alec Ten Harmsel [this message]
2014-11-25 8:36 ` Neil Bothwick
2014-11-25 9:49 ` [gentoo-user] " Andreas K. Huettel
2014-11-25 14:23 ` Alec Ten Harmsel
2014-11-25 15:41 ` Andreas K. Huettel
2014-11-25 17:56 ` Alec Ten Harmsel
2014-11-25 19:38 ` Andreas K. Huettel
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=5473E3C9.9050202@alectenharmsel.com \
--to=alec@alectenharmsel.com \
--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