From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pierre Neidhardt Subject: Re: Packaging Arcan Date: Fri, 23 Nov 2018 12:40:20 +0100 Message-ID: <87h8g8owd7.fsf@ambrevar.xyz> References: 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]:45162) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gQ9ox-0004Pv-OV for guix-devel@gnu.org; Fri, 23 Nov 2018 06:40:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gQ9ou-0005Vh-Kd for guix-devel@gnu.org; Fri, 23 Nov 2018 06:40:27 -0500 Received: from relay12.mail.gandi.net ([217.70.178.232]:44197) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gQ9ou-0005M7-Ca for guix-devel@gnu.org; Fri, 23 Nov 2018 06:40:24 -0500 In-reply-to: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: L p R n d n Cc: guix-devel@gnu.org --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable > 3.a. For qemu, I fear the produced binaries would conflict with the > original ones. Is there something we can do in the build process to deal > with that can of thing or sould we just expect the user deal with it on > its own as Guix doest it very well on its own? The specialized qemu should be an input to arcan, not a propagated input. This way it won't conflict with anything. You might have to configure or patch arcan so that it finds the specialized= qemu binaries in the input store folder. > 3.b. The patched openal is used during build to produce a special binary > (arcan_lwa which allows nested servers). It should normally be fetched > during build time which is obviously not possible here. I suppose there > is no clear answer here but how would you deal with that kind of > behaviour? Create a modified openal package? Can we fetch multiple source= s? This happens a lot with other packages (e.g. the Go build system). The ans= wer is simple: package the specialized OpenAL and provide it as input. If arcan still insists on downloading openal, patch it so that it does not. Hope that helps! =2D-=20 Pierre Neidhardt https://ambrevar.xyz/ --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAEBCAAdFiEEUPM+LlsMPZAEJKvom9z0l6S7zH8FAlv35yQACgkQm9z0l6S7 zH+zBgf9Ft6nvDzthR7yK5k4BeHa83Tl1AnJWDk33J5XHvZeWYSse4Qsh1+ARH9E WzuQsB2xm0+N9yPkm+ktaVfMUk/57FtD1TgU/Y3CNq02UhX4JjLdJPAxomhP4mYb hVuph/HOnlQb+f2mzKeeA3IIJlq+dz+Jvylu5I5KmHDrl5dEc1oBORB9Xyh7R6jJ Rjclcciee6oIJnjaV4V1oX6bmEu4fkDKa6mqs4KIx8Zh6kRx2zSh/djglz/9mYtY u8uUKAgNaZOILYQ+PcxiAr7nxl/ATp4wduwv6Bx5kdGSMC1pWGT8XVdLSA+rZO4I dFMw79Seq0NQWgE93QR9AlmlvlALBQ== =AHid -----END PGP SIGNATURE----- --=-=-=--