public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sean P. Kane" <spkane@genomatica.com>
To: <gentoo-dev@gentoo.org>
Subject: RE: [gentoo-dev] emerge overide options
Date: Fri, 10 May 2002 16:28:44 -0700	[thread overview]
Message-ID: <C42D120999B1CC4C886B6BB2832F356019B33F@HERMES.genomatica.com> (raw)

I like it as a simple way to modify USE flags on the fly (i.e. to work
around a small compile issue), but as it is listed here it could likely
get out of hand quickly, and what happens when you have a use variable
called p, using -p might be confusing even if it is listed after the
ebuild name. Maybe something like a --use-mask="-x +ncurses" would work
and could be masked over the standard USE flags for that build only. The
next questions is does this count for all the dependencies that might
get built as well with that emerge command? Probably should, but could
get people in a bit of trouble if they aren't careful......Of course, so
could a lot of other things.....

Sean


-----Original Message-----
From: david mattatall [mailto:davidsmind@linuxbasics.com] 
Sent: Friday, May 10, 2002 04:12
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] emerge overide options


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.
_______________________________________________
gentoo-dev mailing list
gentoo-dev@gentoo.org
http://lists.gentoo.org/mailman/listinfo/gentoo-dev


             reply	other threads:[~2002-05-10 23:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-10 23:28 Sean P. Kane [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-10 11:12 [gentoo-dev] emerge overide options david mattatall
2002-05-10 23:51 ` Ryan Phillips

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=C42D120999B1CC4C886B6BB2832F356019B33F@HERMES.genomatica.com \
    --to=spkane@genomatica.com \
    --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