public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Andrew Savchenko" <bircoph@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-sound/apulse/
Date: Mon,  1 Oct 2018 09:28:44 +0000 (UTC)	[thread overview]
Message-ID: <1538386116.92e493f6bc3b2fb4eeea5e28be5b26fce106dc50.bircoph@gentoo> (raw)

commit:     92e493f6bc3b2fb4eeea5e28be5b26fce106dc50
Author:     Andrew Savchenko <bircoph <AT> gentoo <DOT> org>
AuthorDate: Mon Oct  1 09:27:52 2018 +0000
Commit:     Andrew Savchenko <bircoph <AT> gentoo <DOT> org>
CommitDate: Mon Oct  1 09:28:36 2018 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=92e493f6

media-sound/apulse: remove surplus src_install call

Remove cmake-utils_src_install from multilib_src_install_all() since
it is already called.

Signed-off-by: Andrew Savchenko <bircoph <AT> gentoo.org>
Package-Manager: Portage-2.3.49, Repoman-2.3.10

 media-sound/apulse/apulse-0.1.12-r4.ebuild | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

diff --git a/media-sound/apulse/apulse-0.1.12-r4.ebuild b/media-sound/apulse/apulse-0.1.12-r4.ebuild
index 46b1d98a51a..b4e49def9d5 100644
--- a/media-sound/apulse/apulse-0.1.12-r4.ebuild
+++ b/media-sound/apulse/apulse-0.1.12-r4.ebuild
@@ -49,10 +49,7 @@ multilib_src_test() {
 }
 
 multilib_src_install_all() {
-	cmake-utils_src_install
-	# The easiest way would be setting MULTILIB_CHOST_TOOLS at global scope, depending
-	# on USE=sdk, but this is no longer permitted, so workaround is required.
-	# See bug 666884 for details.
+	# Do not use deprecated MULTILIB_CHOST_TOOLS
 	if ! use sdk; then
 		unset BUILD_DIR
 		_install_wrapper() { newbin "${BUILD_DIR}/apulse" "${CHOST}-apulse"; }


             reply	other threads:[~2018-10-01  9:28 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-01  9:28 Andrew Savchenko [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-05-20 23:43 [gentoo-commits] repo/gentoo:master commit in: media-sound/apulse/ Sam James
2025-05-20 14:09 Arthur Zamarin
2025-04-19 15:49 Joonas Niilola
2024-08-30 13:11 Andreas Sturmlechner
2024-08-30  5:44 Joonas Niilola
2024-08-30  5:44 Joonas Niilola
2024-06-07 13:15 Joonas Niilola
2024-06-07 13:15 Joonas Niilola
2022-05-01  7:30 Michał Górny
2022-02-21  0:49 Sam James
2022-02-11 16:17 Sam James
2022-02-11 16:14 Sam James
2022-02-11 16:13 Sam James
2020-10-11  7:42 Andrew Savchenko
2020-09-20 20:21 Agostino Sarubbo
2020-09-06 19:10 Andrew Savchenko
2020-08-25 18:20 Georgy Yakovlev
2020-06-27 18:01 Ben Kohler
2020-06-27 16:39 Andrew Savchenko
2018-10-20 11:49 Andrew Savchenko
2018-10-17 16:21 Mikle Kolyada
2018-10-17 12:07 Thomas Deutschmann
2018-09-25 14:26 Andrew Savchenko
2018-09-22 20:53 Andrew Savchenko
2018-08-03 13:05 Andrew Savchenko
2017-08-23  6:42 Andrew Savchenko
2017-08-19  0:31 Thomas Deutschmann
2017-07-15 16:42 Tobias Klausmann
2017-07-09  1:25 Andrew Savchenko
2017-05-06  1:19 Daniel Campbell
2017-05-06  1:14 Daniel Campbell
2017-03-20  4:12 Daniel Campbell
2017-03-20  4:04 Daniel Campbell
2017-03-15  6:24 Daniel Campbell
2016-08-06 14:01 Andrew Savchenko
2016-03-06 22:14 Daniel Campbell
2015-12-25  9:23 Daniel Campbell
2015-08-30  9:47 Daniel Campbell

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=1538386116.92e493f6bc3b2fb4eeea5e28be5b26fce106dc50.bircoph@gentoo \
    --to=bircoph@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