public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: John Mylchreest <johnm@gentoo.org>
To: "Patrick Börjesson" <psycho@rift.ath.cx>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Package-specific USE-flags?
Date: 15 Jul 2003 22:18:16 +0100	[thread overview]
Message-ID: <1058303896.3956.1.camel@johnm.willow.local> (raw)
In-Reply-To: <20030715221803.5111c7f2.psycho@rift.ath.cx>

[-- Attachment #1: Type: text/plain, Size: 2090 bytes --]

On Tue, 2003-07-15 at 21:18, Patrick Börjesson wrote:
> Is there some way to set package-specific USE-flags in some config-file
> somewhere so I don't have to give it manually on the command-line each
> and every time I want to reemerge or upgrade the package? 
> If not, then that functionality would make my life (and probably many
> others too) alot easier. I just did an "update world" and after it
> finished I realised that I had to reemerge a couple of packages since my
> global USE-flags didn't comply with those I wanted for those specific
> packages. For example: I don't want QT-support built-in for most of the
> software on my machine so I have "-qt" in my USE-flag in make.conf, but
> since I want the qt-gui for licq I have to reemerge licq with USE="qt"
> after every single time licq is a part of an "update world". And just
> recently I had to lower the aggressiveness on my CFLAGS to be able to
> emerge mozilla-firebird. I don't want those slack CFLAGS for most of the
> packages in my system so I have to give the CFLAGS manually when
> emerging that package. 
> A suggestion on how to realise it would be package-specific USE-flags in
> make.conf or some other config-file under /etc. For example: If I
> would want qt-support in licq then I'd add LICQ_USE="qt" in make.conf or
> whatever where LICQ_USE is the package-name in uppercase followed by
> _USE. Since there are support for converting strings to uppercase in
> python I don't see a problem in implementing this feature.
> Has there been no request for this feature earlier? Or is there another
> obstacle in the way of implementing it?
> 
> Eagerly awaiting your response,
> Patrick Börjesson
> 
> P.S. Sorry for the long post. D.S.

this has been done by a friend of mine.
if you try searching the bug database for "package specific use flags"
perhaps, or his email (contains alkern) this might find something.
he wrote a portage patch.

Unfortunately i havent got a working browser right now, but it shouldnt
be hard to find. please post back if you couldnt find it.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2003-07-15 21:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-15 20:18 [gentoo-dev] Package-specific USE-flags? Patrick Börjesson
2003-07-15 21:18 ` John Mylchreest [this message]
2003-07-15 22:07   ` Max Kalika
2003-07-15 23:22     ` Patrick Börjesson
2003-07-15 23:32       ` Max Kalika
2003-07-15 23:42         ` Patrick Börjesson
2003-07-15 23:38       ` Patrick Börjesson
2003-07-15 23:44         ` Patrick Börjesson
  -- strict thread matches above, loose matches on Subject: below --
2003-07-15 22:10 Max Kalika

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=1058303896.3956.1.camel@johnm.willow.local \
    --to=johnm@gentoo.org \
    --cc=gentoo-dev@gentoo.org \
    --cc=psycho@rift.ath.cx \
    /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