public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] new profiles.desc header documenting profile/keyword policy
Date: Mon, 20 Jan 2014 02:23:24 -0500	[thread overview]
Message-ID: <201401200223.24912.vapier@gentoo.org> (raw)

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

this has all been fairly ad-hoc in the past, so formalize it in the one place
that impacts everyone -- profiles.desc.
-mike

###############################################################################
# This is a list of valid profiles for each architecture.  This file is used by
# repoman when doing a repoman scan or repoman full.
#
# DO NOT ADD PROFILES WITH A "die" or "exit" IN THEM OR IT KILLS REPOMAN.
#
# Policy statement; updates should be posted to gentoo-dev mailing list.
#
# The meaning of the status field:
#   stable - Fully supported profile; needs dedicated arch team to keep up with
#            stabilization (if using stable KEYWORDS) and keyword requests.
#   dev    - Ideally on track to becoming "stable"; KEYWORDS breakage should be
#            kept to a minimum and bug reports are recommended.
#   exp    - Developers may ignore breakage in these profiles.  It is up to the
#            profile maintainer to keep things viable, but it is not a hard
#            requirement that the deptree stay error free.
# Stable keywords may be used with any of these types.  If an arch only has exp
# profiles, then other developers may ignore that keyword when doing upgrades
# and cleaning out old versions (dropping of stable/unstable KEYWORDS).
#
# Note: Please do not mix tabs & spaces.  Look at surrounding lines first.
#
# File Layout (for exact format, see the portage(5) man page):
#arch           profile_directory                               status

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2014-01-20  7:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20  7:23 Mike Frysinger [this message]
2014-01-20 17:26 ` [gentoo-dev] new profiles.desc header documenting profile/keyword policy William Hubbs
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=201401200223.24912.vapier@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