From: David Corbin <gentoo.org@machturtle.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] USE flag
Date: Thu, 29 Jun 2006 04:46:07 -0400 [thread overview]
Message-ID: <200606290446.07515.gentoo.org@machturtle.com> (raw)
In-Reply-To: <44A3515D.2080306@cs.umn.edu>
On Thursday 29 June 2006 12:04 am, Jeremy Olexa wrote:
> Nick Rout wrote:
> > On Wed, 28 Jun 2006 11:30:26 +0530
> >
> > Aniruddha Shankar wrote:
> >> -----BEGIN PGP SIGNED MESSAGE-----
> >> Hash: SHA1
> >>
> >> Willie Wong wrote:
> >>> Personally speaking, I suggest you emerge 'ufed'.
> >>
> >> I moved from ufed to profuse, it's slightly better with multiple display
> >> interfaces (dialog/ncurses/gtk)
> >>
> >> cheers,
> >
> > funnily enough I dislike the gtk interface and usually start it with
> >
> > DISPLAY= profuse
> >
> > to fool it into thinking X is not available, so it runs in my konsole
>
> Speaking of USE flags this is a PERFECT example of when to
> enable/disable a USE flag. If I was Nick and PREFERRED to start profuse
> without gtk support (aka ncurses) then I would re-emerge profuse WITHOUT
> the gtk USE flag. Thanks for giving some people an example of when to
> enable/disable USE flags, Nick.
>
and what is the correct way to disable the -gtk flag for all future emerges of
a particular ebuild?
Thanks.
David
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-06-29 8:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 2:44 [gentoo-user] USE flag sean
2006-06-28 3:28 ` Willie Wong
2006-06-28 6:00 ` Aniruddha Shankar
2006-06-28 6:58 ` Willie Wong
2006-06-28 20:29 ` sean
2006-06-28 20:41 ` Bo Ørsted Andresen
2006-06-29 0:38 ` Nick Rout
2006-06-29 4:04 ` Jeremy Olexa
2006-06-29 4:49 ` Ryan Tandy
2006-06-29 7:03 ` Jure Varlec
2006-06-29 7:23 ` Jure Varlec
2006-06-30 17:21 ` Jeremy Olexa
2006-06-30 23:11 ` Willie Wong
2006-06-30 23:52 ` Ryan Tandy
2006-06-29 8:46 ` David Corbin [this message]
2006-06-29 9:58 ` Neil Bothwick
2006-07-03 4:29 ` Nick Rout
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=200606290446.07515.gentoo.org@machturtle.com \
--to=gentoo.org@machturtle.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