From: "Conrad Kostecki" <conikost@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-misc/rioutil/
Date: Sat, 7 Dec 2019 01:34:03 +0000 (UTC) [thread overview]
Message-ID: <1575682063.c450f27486c6a0eaf7e9fba59ab0b8a1d64afa17.conikost@gentoo> (raw)
commit: c450f27486c6a0eaf7e9fba59ab0b8a1d64afa17
Author: Conrad Kostecki <conikost <AT> gentoo <DOT> org>
AuthorDate: Sat Dec 7 00:55:29 2019 +0000
Commit: Conrad Kostecki <conikost <AT> gentoo <DOT> org>
CommitDate: Sat Dec 7 01:27:43 2019 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=c450f274
app-misc/rioutil: rework libdir path
Instead of overwriting during src_install to use the correct libpath,
the Makefile is fixed, to use the correct libpath during src_install.
Package-Manager: Portage-2.3.80, Repoman-2.3.19
Signed-off-by: Conrad Kostecki <conikost <AT> gentoo.org>
app-misc/rioutil/rioutil-1.5.4.ebuild | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/app-misc/rioutil/rioutil-1.5.4.ebuild b/app-misc/rioutil/rioutil-1.5.4.ebuild
index 64e2133d8c1..6722b045c2a 100644
--- a/app-misc/rioutil/rioutil-1.5.4.ebuild
+++ b/app-misc/rioutil/rioutil-1.5.4.ebuild
@@ -20,6 +20,9 @@ BDEPEND="virtual/pkgconfig"
src_prepare() {
default
+ # Don't use hardcoded '/lib' libpath
+ sed -e '/libdir/d' -i Makefile.am -i librioutil/Makefile.am || die
+
eautoreconf
}
@@ -28,8 +31,7 @@ src_configure() {
}
src_install() {
- emake DESTDIR="${ED}" libdir="/usr/$(get_libdir)" install
- einstalldocs
+ default
udev_dorules "${FILESDIR}"/75-rio.rules
next reply other threads:[~2019-12-07 1:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-07 1:34 Conrad Kostecki [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-10-11 8:57 [gentoo-commits] repo/gentoo:master commit in: app-misc/rioutil/ Sergei Trofimovich
2020-01-21 10:42 Agostino Sarubbo
2020-01-20 12:52 Agostino Sarubbo
2019-12-07 1:34 Conrad Kostecki
2019-12-05 21:47 Conrad Kostecki
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=1575682063.c450f27486c6a0eaf7e9fba59ab0b8a1d64afa17.conikost@gentoo \
--to=conikost@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