| 1 |
this has all been fairly ad-hoc in the past, so formalize it in the one place |
| 2 |
that impacts everyone -- profiles.desc. |
| 3 |
-mike |
| 4 |
|
| 5 |
############################################################################### |
| 6 |
# This is a list of valid profiles for each architecture. This file is used by |
| 7 |
# repoman when doing a repoman scan or repoman full. |
| 8 |
# |
| 9 |
# DO NOT ADD PROFILES WITH A "die" or "exit" IN THEM OR IT KILLS REPOMAN. |
| 10 |
# |
| 11 |
# Policy statement; updates should be posted to gentoo-dev mailing list. |
| 12 |
# |
| 13 |
# The meaning of the status field: |
| 14 |
# stable - Fully supported profile; needs dedicated arch team to keep up with |
| 15 |
# stabilization (if using stable KEYWORDS) and keyword requests. |
| 16 |
# dev - Ideally on track to becoming "stable"; KEYWORDS breakage should be |
| 17 |
# kept to a minimum and bug reports are recommended. |
| 18 |
# exp - Developers may ignore breakage in these profiles. It is up to the |
| 19 |
# profile maintainer to keep things viable, but it is not a hard |
| 20 |
# requirement that the deptree stay error free. |
| 21 |
# Stable keywords may be used with any of these types. If an arch only has exp |
| 22 |
# profiles, then other developers may ignore that keyword when doing upgrades |
| 23 |
# and cleaning out old versions (dropping of stable/unstable KEYWORDS). |
| 24 |
# |
| 25 |
# Note: Please do not mix tabs & spaces. Look at surrounding lines first. |
| 26 |
# |
| 27 |
# File Layout (for exact format, see the portage(5) man page): |
| 28 |
#arch profile_directory status |
Archives