From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Class-XSAccessor/
Date: Mon, 13 Mar 2023 18:07:03 +0000 (UTC) [thread overview]
Message-ID: <1678730561.288b6bb8969c44590b696afb7a66a7a83a308933.sam@gentoo> (raw)
commit: 288b6bb8969c44590b696afb7a66a7a83a308933
Author: Philippe Chaintreuil <gentoo_bugs_peep <AT> parallaxshift <DOT> com>
AuthorDate: Sun Mar 12 18:05:24 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Mar 13 18:02:41 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=288b6bb8
dev-perl/Class-XSAccessor: rev-bump in prep for adding "~ia64 ~s390"
Those keywords are needed by dev-perl/Moo.
Bug: https://bugs.gentoo.org/898358
Signed-off-by: Philippe Chaintreuil <gentoo_bugs_peep <AT> parallaxshift.com>
Signed-off-by: Sam James <sam <AT> gentoo.org>
.../Class-XSAccessor-1.190.0-r2.ebuild | 32 ++++++++++++++++++++++
1 file changed, 32 insertions(+)
diff --git a/dev-perl/Class-XSAccessor/Class-XSAccessor-1.190.0-r2.ebuild b/dev-perl/Class-XSAccessor/Class-XSAccessor-1.190.0-r2.ebuild
new file mode 100644
index 000000000000..65cc608204c0
--- /dev/null
+++ b/dev-perl/Class-XSAccessor/Class-XSAccessor-1.190.0-r2.ebuild
@@ -0,0 +1,32 @@
+# Copyright 1999-2023 Gentoo Authors
+# Distributed under the terms of the GNU General Public License v2
+
+EAPI=7
+
+DIST_AUTHOR=SMUELLER
+DIST_VERSION=1.19
+inherit perl-module
+
+DESCRIPTION="Generate fast XS accessors without runtime compilation"
+# License note: perl 5-or-newer
+# https://bugs.gentoo.org/718946#c6
+SLOT="0"
+KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~m68k ~mips ~ppc ~ppc64 ~riscv ~sparc ~x86 ~ppc-macos ~x86-solaris"
+IUSE="test"
+RESTRICT="!test? ( test )"
+
+RDEPEND="
+ virtual/perl-Time-HiRes
+ virtual/perl-XSLoader
+"
+BDEPEND="${RDEPEND}
+ virtual/perl-ExtUtils-MakeMaker
+ !dev-perl/Class-XSAccessor-Array
+ test? (
+ virtual/perl-Test-Simple
+ )
+"
+src_compile() {
+ mymake=( "OPTIMIZE=${CFLAGS}" )
+ perl-module_src_compile
+}
next reply other threads:[~2023-03-13 18:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 18:07 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-06-25 4:14 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Class-XSAccessor/ Sam James
2024-06-25 3:57 Sam James
2024-06-25 3:56 Sam James
2024-06-25 3:55 Sam James
2024-06-25 3:54 Sam James
2024-05-23 1:36 Sam James
2023-06-21 9:12 Arthur Zamarin
2023-06-21 8:26 Arthur Zamarin
2023-06-21 8:22 Arthur Zamarin
2023-06-21 8:22 Arthur Zamarin
2023-06-21 8:21 Arthur Zamarin
2023-06-21 8:18 Arthur Zamarin
2023-06-21 8:14 Arthur Zamarin
2023-04-04 22:24 Sam James
2023-03-15 12:32 Arthur Zamarin
2023-03-14 7:03 Arthur Zamarin
2022-05-06 20:03 Arthur Zamarin
2022-05-03 19:47 Arthur Zamarin
2022-05-03 19:47 Arthur Zamarin
2022-02-15 18:31 Matt Turner
2022-01-21 20:12 Arthur Zamarin
2021-12-07 6:14 Joshua Kinard
2021-12-05 21:41 James Le Cuirot
2021-12-04 11:23 Arthur Zamarin
2021-12-04 10:07 Arthur Zamarin
2021-12-04 4:13 Sam James
2021-12-03 20:47 Arthur Zamarin
2020-12-27 14:42 Fabian Groffen
2020-10-04 5:21 Kent Fredric
2020-08-31 14:11 Sam James
2020-08-24 0:08 Sam James
2020-06-20 2:18 Kent Fredric
2015-12-29 23:18 Andreas Hüttel
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=1678730561.288b6bb8969c44590b696afb7a66a7a83a308933.sam@gentoo \
--to=sam@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