From: "Guilherme Amadio" <amadio@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: media-gfx/povray/
Date: Fri, 26 Jul 2019 13:00:13 +0000 (UTC) [thread overview]
Message-ID: <1564145983.1c9d4d04419adae8b6e7db799abbe96b7dc74cdc.amadio@gentoo> (raw)
commit: 1c9d4d04419adae8b6e7db799abbe96b7dc74cdc
Author: Guilherme Amadio <amadio <AT> gentoo <DOT> org>
AuthorDate: Fri Jul 26 12:20:27 2019 +0000
Commit: Guilherme Amadio <amadio <AT> gentoo <DOT> org>
CommitDate: Fri Jul 26 12:59:43 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1c9d4d04
media-gfx/povray: use X11 headers and libraries from prefix
The build system currently hard-codes the X11 include directory
to /usr/include and the library directory to /usr/lib, so the
fix is put unconditionally to fix libdir on non-prefix builds.
Package-Manager: Portage-2.3.69, Repoman-2.3.16
Signed-off-by: Guilherme Amadio <amadio <AT> gentoo.org>
media-gfx/povray/povray-3.7.0.0-r1.ebuild | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/media-gfx/povray/povray-3.7.0.0-r1.ebuild b/media-gfx/povray/povray-3.7.0.0-r1.ebuild
index 2b48c77734e..25d38e4a1bc 100644
--- a/media-gfx/povray/povray-3.7.0.0-r1.ebuild
+++ b/media-gfx/povray/povray-3.7.0.0-r1.ebuild
@@ -1,4 +1,4 @@
-# Copyright 1999-2018 Gentoo Foundation
+# Copyright 1999-2019 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=6
@@ -67,12 +67,14 @@ src_prepare() {
rm -rf libraries || die
- # Change some destination directories that cannot be adjusted via configure
+ # Change some directories that cannot be adjusted via configure
sed \
-e 's:${povsysconfdir}/$PACKAGE/$VERSION_BASE:${povsysconfdir}/'${PN}':g' \
-e 's:${povdatadir}/$PACKAGE-$VERSION_BASE:${povdatadir}/'${PN}':g' \
-e 's:${povdatadir}/doc/$PACKAGE-$VERSION_BASE:${povdatadir}/doc/'${PF}':g' \
-e 's:BOOST_THREAD_LIBS $LIBS:BOOST_THREAD_LIBS $LIBS -lboost_date_time:g' \
+ -e 's:"/usr/include":"'${EPREFIX}'/usr/include":' \
+ -e 's:"/usr/lib":"'${EPREFIX}'/usr/'$(get_libdir)'":' \
-i configure.ac || die
sed \
next reply other threads:[~2019-07-26 13:00 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-26 13:00 Guilherme Amadio [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-08-27 0:44 [gentoo-commits] repo/gentoo:master commit in: media-gfx/povray/ Eli Schwartz
2024-07-28 23:38 Sam James
2024-07-20 11:18 Arthur Zamarin
2024-03-05 4:48 Sam James
2023-12-29 0:32 Sam James
2022-10-08 19:21 Sam James
2022-08-29 18:39 Andreas Sturmlechner
2022-06-16 16:30 Sam James
2022-04-27 21:57 Andreas K. Hüttel
2022-03-01 0:01 Sam James
2022-02-28 23:58 Sam James
2022-02-28 5:45 Sam James
2022-02-28 5:45 Sam James
2022-02-28 5:21 Sam James
2022-02-15 19:51 Sam James
2021-12-06 12:15 David Seifert
2021-07-22 0:19 Marek Szuba
2021-07-21 21:57 Marek Szuba
2021-01-24 2:23 Andreas Sturmlechner
2021-01-06 14:07 Fabian Groffen
2018-06-08 12:20 Guilherme Amadio
2018-02-04 17:41 Andreas Sturmlechner
2016-11-19 9:25 Jeroen Roovers
2016-09-14 7:38 David Seifert
2016-07-05 8:29 Tobias Klausmann
2016-07-04 20:32 David Seifert
2016-07-04 20:22 Justin Lecher
2016-07-01 4:20 Jeroen Roovers
2016-06-10 13:53 Agostino Sarubbo
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=1564145983.1c9d4d04419adae8b6e7db799abbe96b7dc74cdc.amadio@gentoo \
--to=amadio@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