public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] new profiles.desc header documenting profile/keyword policy
Date: Mon, 20 Jan 2014 11:26:13 -0600	[thread overview]
Message-ID: <20140120172613.GA6121@laptop.home> (raw)
In-Reply-To: <201401200223.24912.vapier@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 594 bytes --]

On Mon, Jan 20, 2014 at 02:23:24AM -0500, Mike Frysinger wrote:
> this has all been fairly ad-hoc in the past, so formalize it in the one place
> that impacts everyone -- profiles.desc.
> -mike

If it is policy, shouldn't it go in the dev manual rather than in this
file?

Given that, I have questions:

There are several situations in profiles.desk where one profile is dev
but some profiles that inherit it are exp, for example, the arm
profiles.

Which rule applies in this scenario?

Also, from a maintainer's pov, what is the difference between stable and
dev profiles?

Thanks,

William


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2014-01-20 17:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20  7:23 [gentoo-dev] new profiles.desc header documenting profile/keyword policy Mike Frysinger
2014-01-20 17:26 ` William Hubbs [this message]
2014-01-20 18:18   ` Alexander Berntsen
2014-01-20 18:54     ` William Hubbs
2014-01-20 19:40       ` Markos Chandras
2014-01-21 15:10         ` Tom Wijsman
2014-01-22  6:58     ` Mike Frysinger
2014-01-21 15:05   ` Tom Wijsman
2014-01-22  6:58   ` Mike Frysinger
2014-01-22 23:51     ` Tom Wijsman
2014-01-25 13:35     ` Markos Chandras

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=20140120172613.GA6121@laptop.home \
    --to=williamh@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