public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-libs/ossp-uuid/
Date: Wed, 22 Jun 2022 07:26:13 +0000 (UTC)	[thread overview]
Message-ID: <1655882769.e5750eb623d42ee9f7b7fc523f08894e4fad272c.mgorny@gentoo> (raw)

commit:     e5750eb623d42ee9f7b7fc523f08894e4fad272c
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Wed Jun 22 07:15:06 2022 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Wed Jun 22 07:26:09 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e5750eb6

dev-libs/ossp-uuid: Use the canonical test restriction

While the conditional test restriction here might make some sense
(though it would make even more sense to remove it entirely and just
skip perl tests if USE=-test), it triggers a false positive in pkgcheck
and there's really no need to be that specific to cover a corner case
of a corner case.

Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>

 dev-libs/ossp-uuid/ossp-uuid-1.6.2-r7.ebuild | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)

diff --git a/dev-libs/ossp-uuid/ossp-uuid-1.6.2-r7.ebuild b/dev-libs/ossp-uuid/ossp-uuid-1.6.2-r7.ebuild
index 90dbbbf5b19e..335448aba2c5 100644
--- a/dev-libs/ossp-uuid/ossp-uuid-1.6.2-r7.ebuild
+++ b/dev-libs/ossp-uuid/ossp-uuid-1.6.2-r7.ebuild
@@ -12,6 +12,7 @@ inherit perl-module
 DESCRIPTION="An ISO-C:1999 API with CLI for generating DCE, ISO/IEC and RFC compliant UUID"
 HOMEPAGE="http://www.ossp.org/pkg/lib/uuid/"
 SRC_URI="ftp://ftp.ossp.org/pkg/lib/uuid/${MY_P}.tar.gz"
+S="${WORKDIR}/${MY_P}"
 
 LICENSE="ISC"
 SLOT="0"
@@ -21,9 +22,7 @@ IUSE="+cxx perl static-libs test"
 DEPEND="perl? ( dev-lang/perl test? ( virtual/perl-Test-Simple ) )"
 RDEPEND="perl? ( dev-lang/perl:= )"
 BDEPEND="perl? ( dev-lang/perl )"
-RESTRICT="perl? ( !test? ( test ) )"
-
-S="${WORKDIR}/${MY_P}"
+RESTRICT="!test? ( test )"
 
 PATCHES=(
 	"${FILESDIR}/${P}-gentoo-r1.patch"


             reply	other threads:[~2022-06-22  7:26 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-22  7:26 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-09-19 19:10 [gentoo-commits] repo/gentoo:master commit in: dev-libs/ossp-uuid/ Sam James
2024-10-03 21:25 Sam James
2024-10-03 21:20 Sam James
2022-07-10  7:39 Sam James
2022-07-10  6:20 Agostino Sarubbo
2022-07-10  6:19 Agostino Sarubbo
2022-07-10  6:18 Agostino Sarubbo
2022-07-10  6:17 Agostino Sarubbo
2022-07-09 11:28 Arthur Zamarin
2022-07-09 10:43 Arthur Zamarin
2022-07-09 10:07 David Seifert
2022-07-02 16:19 David Seifert
2022-03-21 17:35 Sam James
2021-01-06 19:34 Fabian Groffen
2019-10-13 19:01 Matt Turner
2018-04-06 11:05 Fabian Groffen
2018-03-22  1:29 Brian Evans
2017-10-30 21:53 Sergei Trofimovich
2017-10-19 19:33 Brian Evans
2017-10-04  8:13 Sergei Trofimovich
2017-09-20 21:17 Sergei Trofimovich
2017-08-29 21:39 Thomas Deutschmann
2017-08-26 12:06 Mikle Kolyada
2017-08-10  4:40 Markus Meier
2017-08-05 18:07 Sergei Trofimovich
2017-07-31 17:56 Brian Evans
2017-01-29 16:19 Fabian Groffen
2016-12-19 13:59 Brian Evans
2016-07-13 12:33 Brian Evans

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=1655882769.e5750eb623d42ee9f7b7fc523f08894e4fad272c.mgorny@gentoo \
    --to=mgorny@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