Gentoo Archives: gentoo-dev

From: Mike Frysinger <vapier@g.o>
To: gentoo-dev@l.g.o
Subject: [gentoo-dev] new profiles.desc header documenting profile/keyword policy
Date: Mon, 20 Jan 2014 07:23:32
Message-Id: 201401200223.24912.vapier@gentoo.org
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

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies