From: Drake Wyrm <wyrm@haell.com>
To: gentoo-portage-dev <gentoo-portage-dev@lists.gentoo.org>
Subject: [gentoo-portage-dev] user-defined classes
Date: Sun, 22 Feb 2004 19:10:45 -0800 [thread overview]
Message-ID: <20040223031045.GD28711@phaenix.haell.com> (raw)
In-Reply-To: <1077440356.1407.158.camel@big_squirt.dol-sen.ca>
[-- Attachment #1: Type: text/plain, Size: 1237 bytes --]
On Sun, 2004-02-22, 00:59:16 -0800, in <1077440356.1407.158.camel@big_squirt.dol-sen.ca>, Brian <dol-sen@telus.net> wrote:
> --include {world,system,myclass1,myclass2,etc.} for portage to add the
> package to whichever list(s) are specified. If myclass is not found,
> then create it and add the pkg. The devs may of course want to exclude
> world(duplication) and system from the acceptable list(used as known
> values for example).
Bonzer idea, mate! Though as a semantics suggestion, I propose
"--add". Portage and the Gentoo initscripts are sufficiently similar
that we may want to maintain the consistency.
In fact, such a change might help to solve some of the FHS issues which
were brought up recently.
/var/db/pkg/ => /var/lib/portage/class/<classname>/
/var/cache/edb/world => /var/lib/portage/class/world/contents
/etc/make.profile/packages => /var/lib/portage/class/system/contents
This may be a difficult change to make right away, due to the many
hard-coded references to /var/db, but is definitely worth keeping in mind
for portage-ng.
--
Batou: Hey, Major... You ever hear of "human rights"?
Kusanagi: I understand the concept, but I've never seen it in action.
--Ghost in the Shell
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2004-02-23 3:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 19:17 [gentoo-portage-dev] user-defined classes Soren Telfer
2004-02-22 8:59 ` Brian
2004-02-22 17:05 ` Max Kalika
2004-02-23 3:10 ` Drake Wyrm [this message]
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=20040223031045.GD28711@phaenix.haell.com \
--to=wyrm@haell.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