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: dev-util/uftrace/
Date: Sat, 31 Jul 2021 00:18:35 +0000 (UTC)	[thread overview]
Message-ID: <1627690626.f6cfe4cff375e3baf2bbfe90e15b7046dab9e967.sam@gentoo> (raw)

commit:     f6cfe4cff375e3baf2bbfe90e15b7046dab9e967
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Jul 25 03:04:11 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Jul 31 00:17:06 2021 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=f6cfe4cf

dev-util/uftrace: [QA] unconditionally install completion files

QA policy [0] says that we don't conditionalise installation of
small files. It's a wasteful rebuild and inconsistent across packages
for when users desire completions to be available.

[0] https://projects.gentoo.org/qa/policy-guide/installed-files.html#pg0301
Signed-off-by: Sam James <sam <AT> gentoo.org>

 dev-util/uftrace/{uftrace-0.10.ebuild => uftrace-0.10-r1.ebuild} | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/dev-util/uftrace/uftrace-0.10.ebuild b/dev-util/uftrace/uftrace-0.10-r1.ebuild
similarity index 91%
rename from dev-util/uftrace/uftrace-0.10.ebuild
rename to dev-util/uftrace/uftrace-0.10-r1.ebuild
index 92c30228011..2b39cc14464 100644
--- a/dev-util/uftrace/uftrace-0.10.ebuild
+++ b/dev-util/uftrace/uftrace-0.10-r1.ebuild
@@ -14,7 +14,7 @@ SRC_URI="https://github.com/namhyung/uftrace/archive/v${PV}.tar.gz -> ${P}.tar.g
 LICENSE="GPL-2"
 SLOT="0"
 KEYWORDS="~amd64 ~arm64"
-IUSE="bash-completion capstone lua"
+IUSE="capstone lua"
 
 REQUIRED_USE="lua? ( ${LUA_REQUIRED_USE} )"
 
@@ -57,6 +57,7 @@ src_compile() {
 
 src_install() {
 	default
+
 	dodoc doc/*.{md,gif,png}
-	use bash-completion && newbashcomp misc/bash-completion.sh uftrace
+	newbashcomp misc/bash-completion.sh uftrace
 }


             reply	other threads:[~2021-07-31  0:18 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-31  0:18 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-02 10:21 [gentoo-commits] repo/gentoo:master commit in: dev-util/uftrace/ Guilherme Amadio
2024-07-03  9:46 Guilherme Amadio
2024-07-03  9:46 Guilherme Amadio
2024-05-30 15:38 Guilherme Amadio
2024-03-05  6:54 Sam James
2024-01-30  8:24 Guilherme Amadio
2024-01-30  8:24 Guilherme Amadio
2024-01-30  8:24 Guilherme Amadio
2023-10-27  6:56 Guilherme Amadio
2023-10-27  6:56 Guilherme Amadio
2023-05-01  0:09 Sam James
2023-02-13  9:56 Guilherme Amadio
2022-09-19 12:11 Guilherme Amadio
2022-09-19 12:11 Guilherme Amadio
2022-09-19 12:11 Guilherme Amadio
2022-03-20  0:38 Sam James
2021-10-10 14:12 Guilherme Amadio
2021-05-31 15:24 Guilherme Amadio
2021-05-31 15:24 Guilherme Amadio
2021-05-31 15:24 Guilherme Amadio
2021-05-24  7:41 Luca Barbato
2020-06-20 17:29 Guilherme Amadio
2020-06-20 17:29 Guilherme Amadio
2020-06-20 17:29 Guilherme Amadio
2019-08-12 19:52 Michał Górny
2019-08-02 13:53 Luca Barbato
2019-07-31  7:32 Luca Barbato
2019-01-27 16:53 Pacho Ramos
2018-11-10 15:13 Sebastian Pipping
2018-07-05 11:34 Manuel Rüger
2018-02-19 15:53 Manuel Rüger

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=1627690626.f6cfe4cff375e3baf2bbfe90e15b7046dab9e967.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