From: "Ryan Phillips" <ryan.phillips@csus.edu>
To: <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] emerge overide options
Date: Fri, 10 May 2002 16:51:25 -0700 (PDT) [thread overview]
Message-ID: <2117.65.106.90.42.1021074685.squirrel@linux.bagwan> (raw)
In-Reply-To: <200205100412.27387.davidsmind@linuxbasics.com>
This appears to work:
USE="-gtk -x ncurses" emerge vim
or
USE="-* ncurses" emerge vim
The later will ignore everything set by /etc/make.conf
but only include ncurses.
What is wrong with this method?
-ryan
> This idea hit me today at school and I wanted to get it to you guys as
> quickly as possible. So without further APU here it is:
>
> emerge vim -o -gtk -x ncurses
>
> This would overide the current settings for gtk x and ncurses in the
> /etc/make.conf file.
>
> emerge vim -O ncurses
>
> What this would do is apply nothing but the ncurses use flag to the
> compile.
>
> What do you think, if you need me to elaborate I could.
next prev parent reply other threads:[~2002-05-10 23:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 11:12 [gentoo-dev] emerge overide options david mattatall
2002-05-10 23:51 ` Ryan Phillips [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-05-10 23:28 Sean P. Kane
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=2117.65.106.90.42.1021074685.squirrel@linux.bagwan \
--to=ryan.phillips@csus.edu \
--cc=gentoo-dev@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