From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:470:142:3::10]:42550) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hrRPL-00029u-A5 for guix-patches@gnu.org; Sat, 27 Jul 2019 14:27:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hrRPK-00009N-6G for guix-patches@gnu.org; Sat, 27 Jul 2019 14:27:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:36586) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hrRPJ-00009B-VF for guix-patches@gnu.org; Sat, 27 Jul 2019 14:27:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hrRPJ-00029C-MD for guix-patches@gnu.org; Sat, 27 Jul 2019 14:27:01 -0400 Subject: [bug#36814] [BONUS PATCH 3/2] gnu: intel-vaapi-driver: Provide LIBVA_DRIVERS_PATH. Resent-Message-ID: From: Marius Bakke In-Reply-To: <20190726184040.31236-1-me@tobias.gr> References: <871rydiifr.fsf@nckx> <20190726184040.31236-1-me@tobias.gr> Date: Sat, 27 Jul 2019 20:26:16 +0200 Message-ID: <87a7cz49mf.fsf@devup.no> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: Tobias Geerinckx-Rice , 36814@debbugs.gnu.org --=-=-= Content-Type: text/plain Tobias Geerinckx-Rice via Guix-patches writes: > * gnu/packages/video.scm (intel-vaapi-driver)[native-search-paths]: > Export LIBVA_DRIVERS_PATH when installed. Can this be squashed into patch 1/2 in this series? > (libva-without-mesa)[native-search-paths]: Don't inherit any. ...and this added in a separate patch, so that the intel-vaapi-driver change does not have to go through 'staging'? > I'm leaving the enormocomment in so I don't have to repeat it here, but I'm less sure about it now than when I wrote it. I thought this was a filthy hack, but maybe it's just mildly unconventional ;-) The documentation is very sparse indeed. The comment could perhaps be shortened by including a link to . --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCgAdFiEEu7At3yzq9qgNHeZDoqBt8qM6VPoFAl08l0gACgkQoqBt8qM6 VPop6Af/Q8Ef3RYNJrcGMExTjCGvp/oMPo+xALTVqpN8gvVXswfUGy6Tyid/bjz4 eSf8CR0jc2LgQQr7YipuQGSxcCKlZ0sLZv8k4MlHq7+OUxyoQjKeB1zFwefEG2u3 tc2O35RHNsRkXm8mMH92KFG6EvkeWqCJ69zSeHeAbSpWyz6BsC9jXlescsR1X908 cZ0KgxzaRXeKQRuBpp/9pf6vwt/XiAm5YDzXDFTaTbfCryECwy1xcqSCIlINVBN0 Ex66oVqxOc0jxVfxBwRqYESZaCOBMSD08dZN4VlK4BngWKlmm6j5TVKR07LKe1pC Jq1Z6lgSFBZILJYyIZ4935wicDX7dg== =Cslr -----END PGP SIGNATURE----- --=-=-=--