public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Fabian Groffen" <grobian@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-perl/Getopt-Long-Descriptive/
Date: Wed, 17 Oct 2018 19:03:17 +0000 (UTC)	[thread overview]
Message-ID: <1539802992.52d66bf82a40b7d5eae357f46281ab8977f84506.grobian@gentoo> (raw)

commit:     52d66bf82a40b7d5eae357f46281ab8977f84506
Author:     Fabian Groffen <grobian <AT> gentoo <DOT> org>
AuthorDate: Wed Oct 17 19:02:36 2018 +0000
Commit:     Fabian Groffen <grobian <AT> gentoo <DOT> org>
CommitDate: Wed Oct 17 19:03:12 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=52d66bf8

dev-perl/Getopt-Long-Descriptive: added Prefix keywords, bug #665088

Signed-off-by: Fabian Groffen <grobian <AT> gentoo.org>
Package-Manager: Portage-2.3.49, Repoman-2.3.11

 .../Getopt-Long-Descriptive/Getopt-Long-Descriptive-0.103.0.ebuild    | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/dev-perl/Getopt-Long-Descriptive/Getopt-Long-Descriptive-0.103.0.ebuild b/dev-perl/Getopt-Long-Descriptive/Getopt-Long-Descriptive-0.103.0.ebuild
index a3cb53187d6..f920a735449 100644
--- a/dev-perl/Getopt-Long-Descriptive/Getopt-Long-Descriptive-0.103.0.ebuild
+++ b/dev-perl/Getopt-Long-Descriptive/Getopt-Long-Descriptive-0.103.0.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2018 Gentoo Foundation
+# Copyright 1999-2018 Gentoo Authors
 # Distributed under the terms of the GNU General Public License v2
 
 EAPI=6
@@ -10,7 +10,7 @@ inherit perl-module
 DESCRIPTION="Getopt::Long with usage text"
 
 SLOT="0"
-KEYWORDS="~amd64 ~arm ~ppc ~x86 ~ppc-aix ~ppc-macos ~x86-solaris"
+KEYWORDS="~amd64 ~arm ~ppc ~x86 ~ppc-aix ~amd64-linux ~x86-linux ~ppc-macos ~x64-macos ~x86-macos ~m68k-mint ~sparc-solaris ~sparc64-solaris ~x64-solaris ~x86-solaris"
 IUSE="test minimal"
 
 CONFLICTS="!<dev-perl/MooseX-Getopt-0.660.0"


             reply	other threads:[~2018-10-17 19:03 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-17 19:03 Fabian Groffen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-10-06 18:39 [gentoo-commits] repo/gentoo:master commit in: dev-perl/Getopt-Long-Descriptive/ Arthur Zamarin
2024-09-23 17:30 Arthur Zamarin
2024-09-23 17:30 Arthur Zamarin
2024-09-23 12:50 Sam James
2024-05-01  3:59 Sam James
2023-08-02 11:58 Arthur Zamarin
2023-07-24  3:27 Sam James
2023-07-24  3:17 Sam James
2023-06-21  4:28 Sam James
2021-10-30 18:46 Andreas K. Hüttel
2021-08-03 11:05 Sam James
2021-08-02  3:22 Sam James
2021-06-05 15:22 Andreas K. Hüttel
2020-09-07 12:00 Yixun Lan
2020-07-20 20:45 Kent Fredric
2018-11-27 21:35 Kent Fredric
2018-11-25  9:43 Mikle Kolyada
2018-11-24 10:49 Sergei Trofimovich
2018-11-23 20:30 Thomas Deutschmann
2018-11-23 13:49 Agostino Sarubbo
2018-09-01 16:59 Andreas Hüttel
2018-09-01 16:59 Andreas Hüttel
2018-08-24 19:37 Markus Meier
2018-06-10 17:11 Thomas Deutschmann
2018-06-10 16:13 Aaron Bauman
2017-10-23  9:29 Kent Fredric
2016-03-09 20:54 Andreas Hüttel
2016-03-05 21:34 Mikle Kolyada
2016-02-20 22:45 Patrice Clement
2016-02-10 20:50 Markus Meier
2016-02-01  8:14 Agostino Sarubbo

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=1539802992.52d66bf82a40b7d5eae357f46281ab8977f84506.grobian@gentoo \
    --to=grobian@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