public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andreas K. Hüttel" <dilfridge@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: virtual/perl-Getopt-Long/
Date: Mon, 13 May 2019 21:10:20 +0000 (UTC)	[thread overview]
Message-ID: <1557781814.ff3c1c9c75fdb7300bfed82ec9f8ea67a07403c0.dilfridge@gentoo> (raw)

commit:     ff3c1c9c75fdb7300bfed82ec9f8ea67a07403c0
Author:     Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
AuthorDate: Mon May 13 21:07:33 2019 +0000
Commit:     Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Mon May 13 21:10:14 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ff3c1c9c

virtual/perl-Getopt-Long: add perl-5.30 as provider

Package-Manager: Portage-2.3.66, Repoman-2.3.12
Signed-off-by: Andreas K. Hüttel <dilfridge <AT> gentoo.org>

 ...rl-Getopt-Long-2.500.0.ebuild => perl-Getopt-Long-2.500.0-r1.ebuild} | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/virtual/perl-Getopt-Long/perl-Getopt-Long-2.500.0.ebuild b/virtual/perl-Getopt-Long/perl-Getopt-Long-2.500.0-r1.ebuild
similarity index 86%
rename from virtual/perl-Getopt-Long/perl-Getopt-Long-2.500.0.ebuild
rename to virtual/perl-Getopt-Long/perl-Getopt-Long-2.500.0-r1.ebuild
index 38cfe35b0dd..c8d864de94b 100644
--- a/virtual/perl-Getopt-Long/perl-Getopt-Long-2.500.0.ebuild
+++ b/virtual/perl-Getopt-Long/perl-Getopt-Long-2.500.0-r1.ebuild
@@ -8,7 +8,7 @@ SLOT="0"
 KEYWORDS="~alpha ~amd64 ~arm ~arm64 ~hppa ~ia64 ~m68k ~mips ~ppc ~ppc64 ~riscv ~s390 ~sh ~sparc ~x86 ~ppc-aix ~x64-cygwin ~amd64-fbsd ~x86-fbsd ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~m68k-mint ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
 
 RDEPEND="
-	|| ( =dev-lang/perl-5.28* ~perl-core/${PN#perl-}-${PV} )
+	|| ( =dev-lang/perl-5.30* =dev-lang/perl-5.28* ~perl-core/${PN#perl-}-${PV} )
 	dev-lang/perl:=
 	!<perl-core/${PN#perl-}-${PV}
 	!>perl-core/${PN#perl-}-${PV}-r999


             reply	other threads:[~2019-05-13 21:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-13 21:10 Andreas K. Hüttel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-01-24 16:25 [gentoo-commits] repo/gentoo:master commit in: virtual/perl-Getopt-Long/ Matt Turner
2024-12-21 20:38 Sam James
2024-12-05 22:26 Sam James
2024-12-01 22:36 Jakov Smolić
2024-12-01 18:33 Arthur Zamarin
2024-12-01 18:33 Arthur Zamarin
2024-12-01 18:33 Arthur Zamarin
2024-12-01 18:33 Arthur Zamarin
2024-12-01 17:35 Jakov Smolić
2024-10-24 13:35 Sam James
2024-09-22 13:53 Sam James
2024-09-17 17:18 Arthur Zamarin
2024-08-31  8:04 Arthur Zamarin
2024-08-29  5:47 Joonas Niilola
2024-05-25 21:56 Andreas K. Hüttel
2024-05-01  3:59 Sam James
2023-06-02 22:26 Andreas K. Hüttel
2023-04-22 12:08 Sam James
2022-05-23 19:05 Andreas K. Hüttel
2021-05-18 22:18 Andreas K. Hüttel
2020-08-04 16:41 Andreas K. Hüttel
2019-05-04 20:06 Andreas K. Hüttel
2017-02-24  5:45 Mike Frysinger
2016-12-21 18:23 Kent Fredric
2016-05-19 18:47 Markus Meier

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=1557781814.ff3c1c9c75fdb7300bfed82ec9f8ea67a07403c0.dilfridge@gentoo \
    --to=dilfridge@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