From: Max Kalika <max+lists.gentoo.dev@lsit.ucsb.edu>
To: "Patrick Börjesson" <psycho@rift.ath.cx>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Package-specific USE-flags?
Date: Tue, 15 Jul 2003 16:32:09 -0700 [thread overview]
Message-ID: <34580000.1058311929@valkyrie.lsit.ucsb.edu> (raw)
In-Reply-To: <20030716012226.0c4a6b5f.psycho@rift.ath.cx>
Quoting Patrick Börjesson <psycho@rift.ath.cx>:
> I must be missing something. I went and downloaded the patch, patched
> /usr/lib/python2.2/site-packages/portage.py, created and edited
> /etc/portage/package.use to my preference (according to the syntax given
> in the bug-page) but emerge --info won't give me the output I want. Is
> there something else I should do in order for it to work?
Did you get the emerge patch as well? Both portage.py and emerge need to
be patched. After this, emerge --info should have a PKGUSE= entry.
> /etc/portage/package.use is attached to see if you can find something
> wrong with it. I began with a _very_ simple config =)
Seems ok.
> By the way, why isn't this feature being incorporated in the official
> portage-release? You've apparently gotten some response from official
> gentoo-developers.
Time, or rather lack thereof, I imagine.
---max kalika
--max@lsit.ucsb.edu
-lsit systems administrator
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-07-15 23:32 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
2003-07-15 22:07 ` Max Kalika
2003-07-15 23:22 ` Patrick Börjesson
2003-07-15 23:32 ` Max Kalika [this message]
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=34580000.1058311929@valkyrie.lsit.ucsb.edu \
--to=max+lists.gentoo.dev@lsit.ucsb.edu \
--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