public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Nick Rout <nick@rout.co.nz>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] USE flag
Date: Mon, 03 Jul 2006 16:29:55 +1200	[thread overview]
Message-ID: <20060703162837.0ACF.NICK@rout.co.nz> (raw)
In-Reply-To: <44A3515D.2080306@cs.umn.edu>


On Wed, 28 Jun 2006 23:04:45 -0500
Jeremy Olexa wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 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.
> 
> DISCLAIMER: I don't use profuse but I assume that the gtk USE flag does
> exactly what I have explained. ;)


You are right and I did think that as i was typing the email! However
there are times when i like the gtk interface, its more a mood thing, so I am happy to leave the gtk flag for that ebuild :-)

-- 
gentoo-user@gentoo.org mailing list



      parent reply	other threads:[~2006-07-03  4:36 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
2006-06-29  9:58           ` Neil Bothwick
2006-07-03  4:29         ` Nick Rout [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=20060703162837.0ACF.NICK@rout.co.nz \
    --to=nick@rout.co.nz \
    --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