public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Benedikt Boehm <hollow@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Valid Profiles
Date: Mon, 1 Aug 2005 17:09:43 +0200	[thread overview]
Message-ID: <200508011709.43801.hollow@gentoo.org> (raw)
In-Reply-To: <1122907586.16102.3.camel@cgianelloni.nuvox.net>

On Monday 01 August 2005 16:46, Chris Gianelloni wrote:
> On Sun, 2005-07-31 at 20:21 +0200, Benedikt Boehm wrote:
> > On Sunday 31 July 2005 16:11, Chris Gianelloni wrote:
> > > ka0ttic reminded me about the idea of adding all of the valid
> > > profiles to profiles.desc now that portage 2.0.51.22 has gone
> > > stable.  Well, I need you guys to give me a list of what is valid or
> > > not.  I have a pretty good idea of what is valid under default-linux,
> > > as far as the default profiles go, but need to know which profiles
> > > are development profiles.  I especially need to know which profiles
> > > are valid for projects like embedded, hardened, and *bsd.
> >
> > vserver/*
>
> Not true.
>
> vserver itself is not a valid profile.  This is exactly why I am asking
> for this information.  From what I can tell, only vserver/x86 is valid.

well, you're right... just thought it's enough to state that everything in 
vserver/ is valid ;)

-- 
He who asks a question is a fool for a minute,
He who doesn't ask is a fool for a lifetime.
-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2005-08-01 15:12 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-31 14:11 [gentoo-dev] Valid Profiles Chris Gianelloni
2005-07-31 14:59 ` Ned Ludd
2005-08-01 14:15   ` Chris Gianelloni
2005-08-01 14:22     ` Mike Frysinger
2005-08-03 23:16       ` Mike Frysinger
2005-07-31 18:21 ` Benedikt Boehm
2005-08-01 14:46   ` Chris Gianelloni
2005-08-01 15:09     ` Benedikt Boehm [this message]
2005-08-01 15:25 ` Kito

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=200508011709.43801.hollow@gentoo.org \
    --to=hollow@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