From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: keywording/
Date: Wed, 17 Feb 2021 09:29:50 +0000 (UTC) [thread overview]
Message-ID: <1613554184.2ad7f77460baef02015ca41032bc86896c9a3a1f.ulm@gentoo> (raw)
commit: 2ad7f77460baef02015ca41032bc86896c9a3a1f
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 14 20:14:58 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Wed Feb 17 09:29:44 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=2ad7f774
keywording: Use "Pure Python" instead of "Pure Perl"
We prefer not to use ALLARCHES for Perl packages because
of how sensitive Perl can be to the underlying host.
While Perl is cross-platform, use of functions which
vary across hosts (e.g. unpack) is quite common.
Let's use Python as an example instead which is
endorsed [0] by Gentoo's Python Project.
[0] https://wiki.gentoo.org/wiki/Project:Python#ALLARCHES
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
keywording/text.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/keywording/text.xml b/keywording/text.xml
index 790a582..9c88cf1 100644
--- a/keywording/text.xml
+++ b/keywording/text.xml
@@ -340,7 +340,7 @@ So packages are not to be marked stable for one of these architectures.
<p>
If you maintain an architecture-independent package (data files, icons, pure
-Perl, ...) then you may request that your package be stabilized on all arches
+Python, ...) then you may request that your package be stabilized on all arches
at once. To do this <d/> when you are filing the stabilization bug <d/> please
add the keyword <c>ALLARCHES</c> in addition to <c>STABLEREQ</c> and CC the
arches that you would like to stabilize.
next reply other threads:[~2021-02-17 9:29 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-17 9:29 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-30 7:59 [gentoo-commits] proj/devmanual:master commit in: keywording/ Ulrich Müller
2025-07-30 7:59 Ulrich Müller
2025-07-30 7:59 Ulrich Müller
2022-03-16 14:52 Sam James
2022-03-14 17:07 Matt Turner
2022-03-10 23:33 Sam James
2022-02-18 18:19 Sam James
2022-01-22 21:35 Sam James
2022-01-22 21:35 Sam James
2022-01-22 21:35 Sam James
2021-10-13 13:42 Ulrich Müller
2021-10-13 13:42 Ulrich Müller
2021-07-16 9:11 Ulrich Müller
2021-07-03 16:21 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-04-07 17:35 Ulrich Müller
2021-03-30 16:10 Ulrich Müller
2021-03-11 13:16 Ulrich Müller
2021-02-17 9:29 Ulrich Müller
2021-02-17 9:29 Ulrich Müller
2021-02-17 9:29 Ulrich Müller
2021-02-15 7:21 Ulrich Müller
2020-07-12 18:32 Ulrich Müller
2020-05-06 7:49 Ulrich Müller
2020-01-25 6:02 Ulrich Müller
2020-01-23 13:50 Ulrich Müller
2018-08-27 15:24 Göktürk Yüksek
2015-06-17 12:05 Ulrich Müller
2015-03-14 9:20 Markos Chandras
2013-02-16 0:03 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=1613554184.2ad7f77460baef02015ca41032bc86896c9a3a1f.ulm@gentoo \
--to=ulm@gentoo.org \
--cc=gentoo-commits@lists.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