[gentoo-commits] proj/devmanual:master commit in: profiles/package.mask/
commit: 15dee0505f502a5eb3a248257b61f02f3f30bee9 Author: Sam James gentoo org> AuthorDate: Tue Mar 15 19:01:59 2022 + Commit: Sam James gentoo org> CommitDate: Wed Mar 16 14:51:48 2022 + URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=15dee050 profiles/package.mask: mention masking development versions Closes: https://bugs.gentoo.org/319927 Signed-off-by: Sam James gentoo.org> profiles/package.mask/text.xml | 19 +++ 1 file changed, 19 insertions(+) diff --git a/profiles/package.mask/text.xml b/profiles/package.mask/text.xml index dd37b9b..299d153 100644 --- a/profiles/package.mask/text.xml +++ b/profiles/package.mask/text.xml @@ -14,6 +14,25 @@ have a comment detailing the specific reason for the mask. The format of the package.mask file is described in man portage. + +Development or unstable (per upstream declaration/categorization) versions of +packages should usually be masked in package.mask. Upstreams may not +deem such releases to be ready for general distribution (or safe to use), or +may not be expecting bug reports from the wider userbase yet. The default +should generally be to mask such versions, but it is acceptable to not mask +in some circumstances e.g. upstream make very infrequent releases, the +changes are safe (reviewed by the Gentoo maintainer), or perhaps other +distributions are shipping the same new version. As an alternative to a +development version, you may also consider backporting required upstream fixes +to the released version. + + + +Overall, masking something and unmasking if it turns out to be stable is +safer (and leads to a better user experience) than the inverse (pushing +unmasked and breakage occurring). + + Entries are added chronologically that is, newer entries should be placed towards the top of the file, underneath any initial
[gentoo-commits] proj/devmanual:master commit in: profiles/package.mask/
commit: 5a14d9bd222a1bde500f9dca32198854f6eaec64 Author: Sam James gentoo org> AuthorDate: Thu Jul 15 00:05:11 2021 + Commit: Sam James gentoo org> CommitDate: Sat Jul 17 04:25:12 2021 + URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=5a14d9bd profiles/package.mask: mention sorting mask entries chronologically Signed-off-by: Sam James gentoo.org> profiles/package.mask/text.xml | 6 ++ 1 file changed, 6 insertions(+) diff --git a/profiles/package.mask/text.xml b/profiles/package.mask/text.xml index 6cef26d..dd37b9b 100644 --- a/profiles/package.mask/text.xml +++ b/profiles/package.mask/text.xml @@ -14,6 +14,12 @@ have a comment detailing the specific reason for the mask. The format of the package.mask file is described in man portage. + +Entries are added chronologically that is, newer entries +should be placed towards the top of the file, underneath any initial +header comment block. + + This file can be used in subprofiles to mask packages only for certain setups.
[gentoo-commits] proj/devmanual:master commit in: profiles/package.mask/
commit: 6872325358f1b9f30273a50e22dabbbfc6ea8034 Author: Ulrich Müller ulm AT gentoo DOT org AuthorDate: Sun May 3 17:21:27 2015 + Commit: Ulrich Müller ulm AT gentoo DOT org CommitDate: Wed May 6 22:06:49 2015 + URL:https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=68723253 Merge package.mask policy from Developer Handbook. This is taken from proj/en/devrel/handbook/hb-policy-ebuild.xml, section QA policy, subsection Masked packages. Permission to reuse the CC-BY-SA-1.0 work under CC-BY-SA-2.0 (or any later version) obtained from author plasmaroo per e-mail on 2015-04-16. profiles/package.mask/text.xml | 11 +++ 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/profiles/package.mask/text.xml b/profiles/package.mask/text.xml index ef57b28..6cef26d 100644 --- a/profiles/package.mask/text.xml +++ b/profiles/package.mask/text.xml @@ -5,10 +5,13 @@ body p -The cpackage.mask/c file can be used to hard mask packages or certain versions -of packages. This is often used when adding certain experimental (either in -ebuild or upstream terms) packages to the tree. The format is described in -cman portage/c. +The cpackage.mask/c file can be used to hard mask packages or +certain versions of packages that should not be merged by users. +This is often used when adding certain experimental (either in ebuild +or upstream terms) packages to the tree, or to prevent merging of +packages that are broken or break something else. Every entry should +have a comment detailing the specific reason for the mask. The format +of the cpackage.mask/c file is described in cman portage/c. /p p
