From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-libs/pcl/
Date: Mon, 15 Feb 2021 00:32:20 +0000 (UTC) [thread overview]
Message-ID: <1613349116.9fa564cb92391a6c80ad1f77e2c227596d52bff0.sam@gentoo> (raw)
commit: 9fa564cb92391a6c80ad1f77e2c227596d52bff0
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Feb 14 23:19:53 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Feb 15 00:31:56 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9fa564cb
sci-libs/pcl: fix double KEYWORDS
Double KEYWORDS lines break tools like ekeyword and Nattka.
As per PMS, blank/empty KEYWORDS is implied by not defining
the variable.
See: https://projects.gentoo.org/qa/policy-guide/ebuild-format.html#pg0105
Package-Manager: Portage-3.0.14, Repoman-3.0.2
Signed-off-by: Sam James <sam <AT> gentoo.org>
sci-libs/pcl/pcl-1.11.1.ebuild | 1 -
sci-libs/pcl/pcl-9999.ebuild | 1 -
2 files changed, 2 deletions(-)
diff --git a/sci-libs/pcl/pcl-1.11.1.ebuild b/sci-libs/pcl/pcl-1.11.1.ebuild
index 4d7299fc43e..b11de25206c 100644
--- a/sci-libs/pcl/pcl-1.11.1.ebuild
+++ b/sci-libs/pcl/pcl-1.11.1.ebuild
@@ -12,7 +12,6 @@ fi
inherit ${SCM} cmake-utils multilib
if [ "${PV#9999}" != "${PV}" ] ; then
- KEYWORDS=""
SRC_URI=""
else
KEYWORDS="~amd64 ~arm"
diff --git a/sci-libs/pcl/pcl-9999.ebuild b/sci-libs/pcl/pcl-9999.ebuild
index 4d7299fc43e..b11de25206c 100644
--- a/sci-libs/pcl/pcl-9999.ebuild
+++ b/sci-libs/pcl/pcl-9999.ebuild
@@ -12,7 +12,6 @@ fi
inherit ${SCM} cmake-utils multilib
if [ "${PV#9999}" != "${PV}" ] ; then
- KEYWORDS=""
SRC_URI=""
else
KEYWORDS="~amd64 ~arm"
next reply other threads:[~2021-02-15 0:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-15 0:32 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-10 16:50 [gentoo-commits] repo/gentoo:master commit in: sci-libs/pcl/ Alexis Ballier
2024-11-25 15:32 Andreas Sturmlechner
2024-11-25 15:32 Andreas Sturmlechner
2024-05-23 8:09 Alexis Ballier
2024-02-19 5:08 Sam James
2024-01-05 10:23 Andrew Ammerlaan
2023-03-03 19:22 Arthur Zamarin
2022-11-13 0:01 David Seifert
2022-09-04 12:23 David Seifert
2022-06-22 14:49 Alexis Ballier
2022-05-19 12:12 Joonas Niilola
2022-03-08 18:03 Alexis Ballier
2021-08-03 7:35 Alexis Ballier
2021-08-03 7:35 Alexis Ballier
2021-08-03 7:35 Alexis Ballier
2021-06-18 19:18 David Seifert
2021-01-05 23:44 Sam James
2020-08-25 14:29 Alexis Ballier
2020-07-03 23:22 Aaron Bauman
2020-07-03 23:22 Aaron Bauman
2020-05-15 16:34 Alexis Ballier
2019-08-30 8:57 Andreas Sturmlechner
2018-12-05 14:50 Alexis Ballier
2017-08-15 5:41 Alexis Ballier
2017-01-26 23:10 Alexis Ballier
2017-01-26 23:10 Alexis Ballier
2016-06-28 10:57 Alexis Ballier
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=1613349116.9fa564cb92391a6c80ad1f77e2c227596d52bff0.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