From: Aaron Walker <ka0ttic@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Identifying inherit-only / usable profiles (round 2)
Date: Tue, 08 Mar 2005 23:56:36 -0500 [thread overview]
Message-ID: <422E8204.6020706@gentoo.org> (raw)
In-Reply-To: <200503080924.04525.vapier@gentoo.org>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Mike Frysinger wrote:
> On Monday 07 March 2005 01:42 pm, Chris Gianelloni wrote:
>
>>Well, since nobody objected, I'm going to add this to portage after the
>>release. I'm probably only going to fill it with the profiles that I am
>>sure are usable, so if I miss something, just add it. I figure it'll be
>>easy enough to add this support to portage and we might as well get the
>>ball rolling by populating the file.
>
>
> i objected on irc, does that count ? :)
>
> why add another file when we already have one (profiles.desc) ?
> unfortunately, repoman will only respect the last entry for each arch, but
> maybe in the future it'll suck less and check all of them ...
> -mike
Isn't profiles.desc just a list of *default* profiles though? We want a list
of all valid profiles. So I think we should either extend profiles.desc to
contain all valid profiles, or add a new file.
Looking at profiles.desc did make me realize something though. If we do
decided to do a separate file, I think we should list the arch as well along
side the profile, kind of like profiles.desc does. This would allow us to get
a list of all valid profiles for a certain arch.
In the case that I need this for (the eclectic profiles module), it'd be much
better IMO to be able to show valid profiles for a certain arch since a valid
profile for sparc is obviously not a valid profile for x86.
Having a format of something like:
alpha default-linux/alpha/2004.3
alpha default-linux/alpha/2005.0
...
x86 default-linux/x86/2004.3
...
would be ideal IMO.
comments?
- --
Yow!
Aaron Walker <ka0ttic@gentoo.org>
[ BSD | cron | forensics | shell-tools | commonbox | netmon | vim | web-apps ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
iD8DBQFCLoIDC3poscuANHARAlfEAJ0f5mbRJb8NnXILKiYfc5xMbbt7agCeJT2F
02McRAEWL3vEaV+ATPG3VK0=
=zsyD
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-03-09 10:33 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-27 22:23 [gentoo-dev] Identifying inherit-only / usable profiles (round 2) Aaron Walker
2005-03-01 10:21 ` Aaron Walker
2005-03-01 14:47 ` Chris Gianelloni
2005-03-01 15:07 ` Aaron Walker
2005-03-07 18:42 ` Chris Gianelloni
2005-03-08 14:24 ` Mike Frysinger
2005-03-09 4:56 ` Aaron Walker [this message]
2005-03-09 16:46 ` Chris Gianelloni
2005-03-09 23:57 ` Jason Stubbs
2005-03-10 0:49 ` Mike Frysinger
2005-03-10 0:50 ` Mike Frysinger
2005-03-10 1:41 ` Jerome Brown
2005-03-10 12:56 ` Aaron Walker
2005-03-10 15:49 ` Chris Gianelloni
2005-03-10 15:53 ` Ciaran McCreesh
2005-03-10 16:27 ` Chris Gianelloni
2005-03-13 18:17 ` Jerome Brown
2005-03-13 20:19 ` Chris Gianelloni
2005-03-13 22:05 ` Martin Schlemmer
2005-03-14 14:43 ` Mike Frysinger
2005-03-10 16:55 ` Lina Pezzella
2005-03-30 9:27 ` Aaron Walker
2005-03-30 14:00 ` Chris Gianelloni
2005-04-01 18:50 ` Aaron Walker
2005-04-01 19:31 ` Mike Frysinger
2005-04-01 19:46 ` Chris Gianelloni
2005-04-01 21:02 ` Mike Frysinger
2005-04-02 6:15 ` Aaron Walker
2005-04-02 7:35 ` Jason Stubbs
2005-04-02 16:41 ` Chris Gianelloni
2005-04-02 16:51 ` Daniel Ostrow
2005-04-03 3:55 ` Jason Stubbs
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=422E8204.6020706@gentoo.org \
--to=ka0ttic@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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