From: Dustin Spicuzza <dustin.spicuzza@wmich.edu>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Additional information to output: emerge -pv
Date: Thu, 25 Aug 2005 18:15:36 +0000 [thread overview]
Message-ID: <430E0AC8.7050200@wmich.edu> (raw)
In-Reply-To: <20050825215737.GN1701@nightcrawler>
>
>Actually, I'd find it useful personally.
>People add *weird* use flags sometimes.
>
>
LoL... yes, thats true.
A suggestion possibly to keep in mind is what if all functionality
related to USE flags were somehow implemented in a seperate class/set of
functions... or maybe that's already being done. But I mean, the job of
determining which flags apply to what package and managing all that and
how it works... I noticed that (at least in stable) a lot of it is in
portage.config, but maybe it could be a seperate class that
portage.config uses.. and other things (like deps, etc). Then stuff like
outputting USE flags, or adding additional ways to determine which USE
flags to actually use for each package, would all be in one location,
lending itself to code reuse...
Of course, this is just from my looking at portage stable for a week or
so... maybe its already being done. :)
Dustin
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-25 22:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 17:44 Re: [gentoo-portage-dev] Additional information to output: emerge -pv Dustin Spicuzza
2005-08-25 21:57 ` Brian Harring
2005-08-25 18:15 ` Dustin Spicuzza [this message]
2005-08-25 22:24 ` Brian Harring
-- strict thread matches above, loose matches on Subject: below --
2005-08-25 17:54 Dustin Spicuzza
2005-08-25 18:22 ` Thomas de Grenier de Latour
2005-08-25 2:15 Dustin Spicuzza
2005-08-25 9:58 ` Simon Stelling
2005-08-25 9:59 ` Paul de Vrieze
2005-08-25 14:15 ` Sandy McArthur
2005-08-25 16:14 ` Brian Harring
2005-08-25 16:28 ` Brian Harring
2005-08-25 20:42 ` Alec Warner
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=430E0AC8.7050200@wmich.edu \
--to=dustin.spicuzza@wmich.edu \
--cc=gentoo-portage-dev@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