public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jason Stubbs <jstubbs@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] Identifying inherit-only / usable profiles (round 2)
Date: Thu, 10 Mar 2005 08:57:27 +0900	[thread overview]
Message-ID: <200503100857.27412.jstubbs@gentoo.org> (raw)
In-Reply-To: <1110386764.9520.262.camel@cgianelloni.nuvox.net>

On Thursday 10 March 2005 01:46, Chris Gianelloni wrote:
> On Tue, 2005-03-08 at 23:56 -0500, Aaron Walker wrote:
> > 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.
>
> Either way would be fine by me, but portage would have to be modified to
> allow for multiple profiles to be listed per arch in profiles.desc

It won't break anything if that's what you're worried about. The only thing 
that uses profiles.desc is repoman, which can "handle" multiple profiles 
listed. ... I just found that all duplicates have been removed from 
profiles.desc. I guess people don't like noise. ;)

Okay. For the time being, there's a two things that can be done with repoman. 
It could print out a table of the profiles it will use for scanning or add 
the profile that was checked against into the arch-based failure message. 
What do you think?

Regards,
Jason Stubbs
--
gentoo-dev@gentoo.org mailing list


  reply	other threads:[~2005-03-09 23:58 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
2005-03-09 16:46             ` Chris Gianelloni
2005-03-09 23:57               ` Jason Stubbs [this message]
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=200503100857.27412.jstubbs@gentoo.org \
    --to=jstubbs@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