From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: bug#32770: Packaging SLIME/SWANK as Common Lisp library Date: Thu, 04 Oct 2018 22:38:26 +0200 Message-ID: <87a7ntmoql.fsf@ambrevar.xyz> References: <87museeyy5.fsf@ambrevar.xyz> <20180929151630.00cf6396@mailservices.uwaterloo.ca> <87lg7iwu9i.fsf@ambrevar.xyz> <87k1n2wten.fsf@ambrevar.xyz> <20181002045531.78223c72@mailservices.uwaterloo.ca> <878t3gwsrm.fsf@ambrevar.xyz> <20181003012224.5baff3ac@mailservices.uwaterloo.ca> <8736tmj2vj.fsf@ambrevar.xyz> <20181004010308.7825505f@mailservices.uwaterloo.ca> <87k1mym7kb.fsf@ambrevar.xyz> <87zhvtshy9.fsf@elephly.net> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:54728) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1g8AOq-00017t-9p for bug-guix@gnu.org; Thu, 04 Oct 2018 16:39:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1g8AOj-0007kq-Ot for bug-guix@gnu.org; Thu, 04 Oct 2018 16:39:08 -0400 Received: from debbugs.gnu.org ([208.118.235.43]:32844) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1g8AOj-0007kc-L3 for bug-guix@gnu.org; Thu, 04 Oct 2018 16:39:01 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1g8AOj-0006Zw-I6 for bug-guix@gnu.org; Thu, 04 Oct 2018 16:39:01 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-reply-to: <87zhvtshy9.fsf@elephly.net> List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ricardo Wurmus Cc: 32770@debbugs.gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable > This sounds useful, but to me it feels like wrapping executables in > LD_LIBRARY_PATH, which we try hard to avoid. >=20 > When using cffi:*foreign-library-directories* how would we deal with > cases where we have more than one package specifying cffi-packages? > Would this option need to be considered for every package in the package > closure? Would it need to be handled by a profile hook in case these > packages are installed? Every new path is appended to the list, and CFFI looks for the first matchi= ng library. This means that there could be conflicts if two packages feature = the same library name (which could be the case when a library is built with different flags for instance). I think you are right, we should go with Andy's approach. =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAlu2ekIACgkQm9z0l6S7 zH8fEQf8DRqneYkp57M1bx9AUhRyQdzjSxTHnFM8xG5C9KXt4jYuFTDnLitOrjkg 6tF/eqoZYyK8eYfHzGjvu7x329B+4b7JC6O3r80Xnp/wAkpsVMP+RmhijSmM6SB9 lnkx2yRXLTfQuNLg0WLgpssEq981f1soL6IQSpdlSgUR79bKorWyiYc5Dz3aIfix +7fJPkTsqL1yI5NSI/CstxmZOMG0gq2AXWwqQfq5tOjVa15j8Ko2WZt9gPiZhjRx qmifhIKVJaZD2KO28Rva5IG3+HdNbGpjYwwSrOWv3UFHl6Z9jG/iVU4qC8NSJKX2 jIqZcvqKdDfPkl3jhLQJg8YMxdX63w== =vo2x -----END PGP SIGNATURE----- --=-=-=--