public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jeremy Olexa <olexa@cs.umn.edu>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] USE flag
Date: Fri, 30 Jun 2006 12:21:06 -0500	[thread overview]
Message-ID: <44A55D82.8000409@cs.umn.edu> (raw)
In-Reply-To: <44A35BEB.7010600@gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ryan Tandy wrote:
> Jeremy Olexa wrote:
>> without gtk support (aka ncurses) then I would re-emerge profuse WITHOUT
> 
> Er... maybe I misunderstood something, but gtk and ncurses are two
> COMPLETELY different things.

right. that is what I meant. if you didn't want a gtk interface you
would end up using a ncurses interface ;) yes?

- --
Jeremy Olexa
(olexa@cs.umn.edu)
Office: EE/CS 1-201
CS/IT Systems Staff
University of Minnesota

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFEpV2BFN7pD9kMi/URAjtwAKCLGn/3pLhjbZfIpnl8vv21nyw43ACfQk5Y
qVfOijhX61Q/6JL9yGpToJA=
=mND0
-----END PGP SIGNATURE-----
-- 
gentoo-user@gentoo.org mailing list



  parent reply	other threads:[~2006-06-30 17:32 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 [this message]
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

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=44A55D82.8000409@cs.umn.edu \
    --to=olexa@cs.umn.edu \
    --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