[gentoo-commits] proj/policy-guide:master commit in: /

["Sam James" <sam@gentoo.org>]

commit:     2247c2a5af859d56a7ea776134de3b62054f6f3c
Author:     Petr Vaněk <arkamar <AT> atlas <DOT> cz>
AuthorDate: Mon Sep 25 07:05:26 2023 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Jul 13 04:07:19 2025 +0000
URL:        https://gitweb.gentoo.org/proj/policy-guide.git/commit/?id=2247c2a5

basic: declare repoman as deprecated

This change reflects the fact that repoman was deprecated in ::gentoo.

Bug: https://bugs.gentoo.org/835013
Signed-off-by: Petr Vaněk <arkamar <AT> atlas.cz>
Part-of: https://github.com/gentoo/policy-guide/pull/25
Closes: https://github.com/gentoo/policy-guide/pull/25
Signed-off-by: Sam James <sam <AT> gentoo.org>

 basics.rst | 15 +++++++--------
 1 file changed, 7 insertions(+), 8 deletions(-)

diff --git a/basics.rst b/basics.rst
index 77233d7..cdef1e7 100644
--- a/basics.rst
+++ b/basics.rst
@@ -27,19 +27,18 @@ Policy compliance checking
 Currently, there are two kinds of tools involved in detecting policy
 violations:
 
-1. Linting-class tools, including repoman_ and pkgcheck_.  Those tools
-   analyze ebuilds and other files in the package repository for known
-   policy violations.  They are limited to checking for problems that
-   can be detected without running the phase functions.
+1. Linting-class tools, including pkgcheck_ and deprecated repoman_.
+   Those tools analyze ebuilds and other files in the package repository
+   for known policy violations.  They are limited to checking for
+   problems that can be detected without running the phase functions.
 
 2. Build- and install-time QA checks, implemented in package managers.
    Those trigger while the ebuilds are executing.  They are limited
    to testing the currently running code path.
 
 Developers are expected to use both kinds of tools before pushing their
-commits.  They should both lint the changed ebuilds using repoman_
-or pkgcheck_, and test whether their packages build and install
-correctly.
+commits.  They should both lint the changed ebuilds using pkgcheck_, and
+test whether their packages build and install correctly.
 
 Additionally, Gentoo is running pkgcheck_ periodically as `Gentoo CI`_.
 All non-trivial violations are reported to the gentoo-automated-testing_
@@ -78,8 +77,8 @@ asked to override the policy.  All QA decisions and policies can further
 be appealed to the Council_.
 
 
-.. _repoman: https://wiki.gentoo.org/wiki/Repoman
 .. _pkgcheck: https://github.com/pkgcore/pkgcheck
+.. _repoman: https://wiki.gentoo.org/wiki/Repoman
 .. _Gentoo CI: https://qa-reports.gentoo.org/output/gentoo-ci/output.html
 .. _gentoo-automated-testing: https://archives.gentoo.org/gentoo-automated-testing/
 .. _QA team: https://wiki.gentoo.org/wiki/Project:Quality_Assurance