public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Matthias Maier" <tamiko@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-php/libvirt-php/
Date: Tue, 16 Aug 2016 05:22:14 +0000 (UTC)	[thread overview]
Message-ID: <1471324924.9da931e699af972059d1c9f72e4629561b832a37.tamiko@gentoo> (raw)

commit:     9da931e699af972059d1c9f72e4629561b832a37
Author:     Matthias Maier <tamiko <AT> gentoo <DOT> org>
AuthorDate: Tue Aug 16 03:04:52 2016 +0000
Commit:     Matthias Maier <tamiko <AT> gentoo <DOT> org>
CommitDate: Tue Aug 16 05:22:04 2016 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=9da931e6

dev-php/libvirt-php: Update live build, bug #588218

Thanks to Michal Privoznik for the updated ebuild

Package-Manager: portage-2.2.28

 dev-php/libvirt-php/libvirt-php-9999.ebuild | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/dev-php/libvirt-php/libvirt-php-9999.ebuild b/dev-php/libvirt-php/libvirt-php-9999.ebuild
index f599904..737b997 100644
--- a/dev-php/libvirt-php/libvirt-php-9999.ebuild
+++ b/dev-php/libvirt-php/libvirt-php-9999.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2014 Gentoo Foundation
+# Copyright 1999-2016 Gentoo Foundation
 # Distributed under the terms of the GNU General Public License v2
 # $Id$
 
@@ -6,7 +6,7 @@ EAPI=5
 
 PHP_EXT_NAME="libvirt-php"
 PHP_EXT_SKIP_PHPIZE="yes"
-USE_PHP="php5-6 php5-5 php5-4"
+USE_PHP="php5-6 php5-5"
 # Automake 1.14 is broken.  Check this later
 WANT_AUTOMAKE="1.13"
 
@@ -22,7 +22,8 @@ KEYWORDS=""
 IUSE="doc"
 
 RDEPEND="app-emulation/libvirt
-	dev-libs/libxml2"
+	dev-libs/libxml2
+	dev-php/pecl-imagick"
 DEPEND="${RDEPEND}
 	dev-libs/libxslt
 	doc? ( app-text/xhtml1 )"
@@ -53,7 +54,7 @@ src_install() {
 	for slot in $(php_get_slots); do
 		php_init_slot_env ${slot}
 		insinto "${EXT_DIR}"
-		newins "src/${PHP_EXT_NAME}.so" "${PHP_EXT_NAME}.so"
+		newins "src/.libs/${PHP_EXT_NAME}.so" "${PHP_EXT_NAME}.so"
 	done
 	php-ext-source-r2_createinifiles
 	dodoc AUTHORS ChangeLog NEWS README


             reply	other threads:[~2016-08-16  5:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-16  5:22 Matthias Maier [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-11-10  1:53 [gentoo-commits] repo/gentoo:master commit in: dev-php/libvirt-php/ Michael Orlitzky
2024-11-10  1:53 Michael Orlitzky
2024-10-17  5:01 Sam James
2024-10-17  5:01 Sam James
2024-03-14  5:54 Sam James
2022-12-24  7:03 Sam James
2022-12-24  7:03 Sam James
2022-10-28 19:15 Sam James
2022-08-19  2:40 Sam James
2022-06-15 22:06 Sam James
2022-03-22  3:14 Brian Evans
2022-03-18 16:53 Brian Evans
2022-03-16 22:42 Brian Evans
2021-05-28 15:57 David Seifert
2021-03-03 17:40 Sam James
2021-01-21 18:08 Brian Evans
2020-06-14 23:30 Thomas Deutschmann
2019-12-05 20:25 Brian Evans
2019-06-07 14:14 Thomas Deutschmann
2018-04-11  1:28 Brian Evans
2018-03-22 17:26 Brian Evans
2017-10-19 19:39 Brian Evans
2017-08-18 18:28 Michael Orlitzky
2017-07-11 15:26 Brian Evans
2017-07-02  2:31 Brian Evans
2016-08-16  5:22 Matthias Maier
2016-08-16  5:22 Matthias Maier
2016-08-16  5:22 Matthias Maier

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=1471324924.9da931e699af972059d1c9f72e4629561b832a37.tamiko@gentoo \
    --to=tamiko@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