From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] useful profiles.desc
Date: Sat, 5 Nov 2005 20:37:42 +0000 [thread overview]
Message-ID: <20051105203742.GB11335@toucan.gentoo.org> (raw)
In-Reply-To: <1131215695.27346.25.camel@vertigo.twi-31o2.org>
On Sat, Nov 05, 2005 at 01:34:55PM -0500, Chris Gianelloni wrote:
> On Sat, 2005-11-05 at 09:23 -0500, Aaron Walker wrote:
> > Continuing a subject I've brought up several times in the past...
> >
> > Are we any closer to having a profiles.desc that lists all valid profiles?
> > IIRC the current stable portage should be ok with it. Are there any other
> > issues preventing this from becoming a reality?
>
> Also, what are the valid "status" entries? Is it just dev and stable?
well, repoman only cares about "dev", but yes, those are the only two status
values we are using atm
-mike
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-05 20:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-05 14:23 [gentoo-dev] useful profiles.desc Aaron Walker
2005-11-05 18:34 ` Chris Gianelloni
2005-11-05 20:37 ` Mike Frysinger [this message]
2005-11-06 2:53 ` Aaron Walker
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=20051105203742.GB11335@toucan.gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-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