public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sci-electronics/kicad-meta/
Date: Mon, 29 Nov 2021 01:58:25 +0000 (UTC)	[thread overview]
Message-ID: <1638151015.5b9388b0ce05158247f7a24a2c3faa9bb7394aaa.sam@gentoo> (raw)

commit:     5b9388b0ce05158247f7a24a2c3faa9bb7394aaa
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Nov 29 01:56:55 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Nov 29 01:56:55 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5b9388b0

sci-electronics/kicad-meta: drop keywords for 6.0.0_rc1

While upstream have quite a slow release cadence (which is why I was open to adding
the RC), we should probably avoid exposing the RC to people by default.

Drop keywords for _rc versions (for now, anyway).

Bug: https://bugs.gentoo.org/827816
Signed-off-by: Sam James <sam <AT> gentoo.org>

 sci-electronics/kicad-meta/kicad-meta-6.0.0_rc1.ebuild | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/sci-electronics/kicad-meta/kicad-meta-6.0.0_rc1.ebuild b/sci-electronics/kicad-meta/kicad-meta-6.0.0_rc1.ebuild
index a8d3fb5f049a..6b4df29aa26f 100644
--- a/sci-electronics/kicad-meta/kicad-meta-6.0.0_rc1.ebuild
+++ b/sci-electronics/kicad-meta/kicad-meta-6.0.0_rc1.ebuild
@@ -9,7 +9,11 @@ SRC_URI=""
 
 LICENSE="metapackage"
 SLOT="0"
-KEYWORDS="~amd64 ~arm64 ~x86"
+
+if [[ ${PV} != *_rc ]] ; then
+	KEYWORDS="~amd64 ~arm64 ~x86"
+fi
+
 IUSE="doc minimal"
 
 RDEPEND="


             reply	other threads:[~2021-11-29  1:58 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-29  1:58 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-24  5:22 [gentoo-commits] repo/gentoo:master commit in: sci-electronics/kicad-meta/ Yixun Lan
2024-08-23  9:30 Joonas Niilola
2024-08-22 11:40 Yixun Lan
2024-08-09  3:05 Yixun Lan
2024-06-11 20:45 Sam James
2024-05-03 13:13 Andrew Ammerlaan
2024-03-18  7:35 Joonas Niilola
2024-03-17 23:12 Yixun Lan
2024-03-17 23:12 Yixun Lan
2024-02-28 11:03 Yixun Lan
2024-01-31 10:22 Yixun Lan
2023-11-28 16:38 Joonas Niilola
2023-11-28 16:38 Joonas Niilola
2023-11-10  9:16 Joonas Niilola
2023-10-28 14:22 Yixun Lan
2023-09-23  9:50 Sam James
2023-09-23  9:50 Sam James
2023-09-23  9:50 Sam James
2023-07-18 19:15 Sam James
2023-07-18 19:15 Sam James
2023-07-18 19:15 Sam James
2023-04-25  0:35 Sam James
2023-04-19 17:50 Matthew Smith
2023-04-19 17:50 Matthew Smith
2023-02-17  5:14 Sam James
2023-02-17  5:14 Sam James
2023-02-17  5:14 Sam James
2023-02-08 23:54 Marek Szuba
2023-01-27  7:46 Joonas Niilola
2022-11-06  8:53 Matthew Smith
2022-11-06  8:53 Matthew Smith
2022-11-05  9:10 Matthew Smith
2022-09-08 14:33 Agostino Sarubbo
2022-08-25 10:33 Matthew Smith
2022-06-21 20:44 Sam James
2022-06-10  7:51 Sam James
2022-03-25 11:03 Joonas Niilola
2022-03-21 23:42 Sam James
2022-01-21 19:11 Sam James
2021-12-27  1:08 Sam James
2021-12-04 11:31 Joonas Niilola
2021-12-04 11:31 Joonas Niilola
2021-11-29  2:01 Sam James
2021-11-23 17:15 Sam James
2021-11-17 10:54 Joonas Niilola
2021-06-04 23:22 Sam James
2021-02-22 18:57 Sam James
2021-01-18 10:14 David Seifert
2021-01-11 10:27 Alexey Shvetsov
2020-11-19 10:22 Joonas Niilola
2020-06-06 17:47 Alexey Shvetsov
2020-06-06 17:47 Alexey Shvetsov
2020-05-14 10:36 Alexey Shvetsov
2019-12-17 18:14 Joonas Niilola
2019-08-10 11:15 Joonas Niilola
2019-06-04 12:47 Virgil Dupras
2019-04-07 16:53 Alexey Shvetsov
2019-01-02 16:51 Amy Liffey
2018-09-07  3:03 Virgil Dupras
2018-09-07  3:03 Virgil Dupras

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=1638151015.5b9388b0ce05158247f7a24a2c3faa9bb7394aaa.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