public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Pacho Ramos" <pacho@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-misc/virtualgl/
Date: Sun, 20 Sep 2015 08:23:12 +0000 (UTC)	[thread overview]
Message-ID: <1442737383.fed12a1bc95a7a7d4409b47af7ce0f2b9f48b685.pacho@gentoo> (raw)

commit:     fed12a1bc95a7a7d4409b47af7ce0f2b9f48b685
Author:     Pacho Ramos <pacho <AT> gentoo <DOT> org>
AuthorDate: Sun Sep 20 08:23:03 2015 +0000
Commit:     Pacho Ramos <pacho <AT> gentoo <DOT> org>
CommitDate: Sun Sep 20 08:23:03 2015 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=fed12a1b

x11-misc/virtualgl: Fix docdir path

Package-Manager: portage-2.2.20.1

 x11-misc/virtualgl/virtualgl-2.4.1-r1.ebuild | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/x11-misc/virtualgl/virtualgl-2.4.1-r1.ebuild b/x11-misc/virtualgl/virtualgl-2.4.1-r1.ebuild
index 926a7d7..f271f99 100644
--- a/x11-misc/virtualgl/virtualgl-2.4.1-r1.ebuild
+++ b/x11-misc/virtualgl/virtualgl-2.4.1-r1.ebuild
@@ -49,7 +49,7 @@ src_configure() {
 	abi_configure() {
 		local mycmakeargs=(
 			$(cmake-utils_use ssl VGL_USESSL)
-			-DVGL_DOCDIR=/usr/share/doc/"${P}"
+			-DVGL_DOCDIR=/usr/share/doc/"${PF}"
 			-DTJPEG_INCLUDE_DIR=/usr/include
 			-DVGL_LIBDIR=/usr/$(get_libdir)
 			-DTJPEG_LIBRARY=/usr/$(get_libdir)/libturbojpeg.so


             reply	other threads:[~2015-09-20  8:23 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-20  8:23 Pacho Ramos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-12-04  9:43 [gentoo-commits] repo/gentoo:master commit in: x11-misc/virtualgl/ Anthony G. Basile
2016-06-10 15:32 Agostino Sarubbo
2016-09-29 17:45 Pacho Ramos
2016-10-16  8:23 Pacho Ramos
2016-10-22  7:54 Pacho Ramos
2017-04-08  9:09 Ettore Di Giacinto
2017-04-08  9:09 Ettore Di Giacinto
2017-10-16  3:34 David Seifert
2017-11-02 21:16 Thomas Deutschmann
2017-11-07 13:17 Manuel Rüger
2018-06-06  8:13 Andreas Sturmlechner
2018-06-09 14:15 Mart Raudsepp
2019-01-11 21:31 Craig Andrews
2019-01-11 21:31 Craig Andrews
2019-05-01 23:35 Craig Andrews
2019-06-05  6:48 Agostino Sarubbo
2019-06-05  7:46 Agostino Sarubbo
2019-06-05  9:19 Andreas Sturmlechner
2019-11-18 11:50 Agostino Sarubbo
2019-11-19 12:48 Agostino Sarubbo
2019-11-20 12:22 Andreas Sturmlechner
2020-06-04 20:36 Pacho Ramos
2020-06-04 20:36 Pacho Ramos
2020-06-06 15:58 Pacho Ramos
2020-06-27 10:48 Pacho Ramos
2020-06-27 10:48 Pacho Ramos
2020-07-24 12:23 Sam James
2020-07-25 14:16 Pacho Ramos
2020-11-29 11:45 Pacho Ramos
2020-11-29 11:45 Pacho Ramos
2021-02-14 19:52 Sam James
2021-03-25 15:42 Sam James
2021-03-26 11:25 Sam James
2021-04-12 17:33 Sam James
2021-04-12 17:33 Sam James
2021-05-01  9:53 Mikle Kolyada
2021-05-08  9:27 Pacho Ramos
2021-05-08  9:27 Pacho Ramos
2021-05-08  9:27 Pacho Ramos
2021-12-21 18:25 Pacho Ramos
2021-12-22 10:30 Pacho Ramos
2022-05-04 22:32 Sam James
2022-05-04 22:32 Sam James
2022-05-22 11:04 Pacho Ramos
2022-05-22 11:04 Pacho Ramos
2022-07-10 14:39 Sam James
2022-08-15 16:43 Andreas Sturmlechner
2022-08-16  5:32 Joonas Niilola
2022-08-16  5:32 Joonas Niilola
2022-10-23 16:17 Pacho Ramos
2022-10-23 16:17 Pacho Ramos
2022-12-01 22:24 Jakov Smolić
2022-12-01 22:28 Jakov Smolić
2023-04-17 13:30 Pacho Ramos
2023-04-17 13:30 Pacho Ramos
2024-05-18 10:16 Pacho Ramos
2024-05-18 10:16 Pacho Ramos
2024-05-18 10:16 Pacho Ramos
2024-05-18 15:35 Sam James
2024-05-18 16:08 Sam James
2024-07-12 17:23 Arthur Zamarin
2024-07-12 17:23 Arthur Zamarin
2024-12-20 11:21 Pacho Ramos
2025-04-13 16:44 Pacho Ramos
2025-04-14  6:12 Joonas Niilola
2025-04-14  7:05 Joonas Niilola
2025-05-28 12:49 Pacho Ramos
2025-05-28 12:49 Pacho Ramos
2025-06-22 18:03 Arthur Zamarin
2025-10-12  8:37 Pacho Ramos
2025-10-12  8:37 Pacho Ramos

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=1442737383.fed12a1bc95a7a7d4409b47af7ce0f2b9f48b685.pacho@gentoo \
    --to=pacho@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