From: Michael Tindal <mtindal@paradoxpoint.com>
To: gentoo-portage-dev@lists.gentoo.org
Subject: [gentoo-portage-dev] Re: Portage API
Date: Tue, 19 Oct 2004 04:53:03 -0400 [thread overview]
Message-ID: <1098175983.18550.9.camel@localhost> (raw)
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
Hey Jason,
As you know, I'm currently working on a tool to manage /etc/portage
easily, to help users. Tentatively named emod, it has the synopsis
emod mask|unmask|keyword|inject [--include-deps] [--category] blah1
blah2...
Well, for the first optional argument, emod needs access to portage's
dependency information. It would need to know what versions the package
depended on, whether those packages could be sastified by "keyword"
instead of "~keyword", and if emod is at one point extended to combine
the functionality of euse, ie adding an |use mode, it would also need
access to every package's dependencies IUSE settings to determine
whether or not the given use was valid for deps.
Thats all I can think of for right now, if I come up with more I'll let
you know.
Mike Tindal
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-10-19 8:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1098175983.18550.9.camel@localhost \
--to=mtindal@paradoxpoint.com \
--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