From mboxrd@z Thu Jan 1 00:00:00 1970 From: L p R n d n Subject: Re: Packaging Arcan Date: Fri, 23 Nov 2018 13:54:39 +0100 Message-ID: References: <87h8g8owd7.fsf@ambrevar.xyz> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50333) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gQAAn-0002ce-Ve for guix-devel@gnu.org; Fri, 23 Nov 2018 07:03:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gQA2k-0008H3-Bz for guix-devel@gnu.org; Fri, 23 Nov 2018 06:54:45 -0500 Received: from mout01.posteo.de ([185.67.36.141]:48986) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gQA2i-00086T-Lw for guix-devel@gnu.org; Fri, 23 Nov 2018 06:54:41 -0500 Received: from submission (posteo.de [89.146.220.130]) by mout01.posteo.de (Postfix) with ESMTPS id 4C72616005E for ; Fri, 23 Nov 2018 12:54:38 +0100 (CET) In-Reply-To: <87h8g8owd7.fsf@ambrevar.xyz> (Pierre Neidhardt's message of "Fri, 23 Nov 2018 12:40:20 +0100") 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: Pierre Neidhardt Cc: guix-devel@gnu.org Thanks Pierre for your quick answer! Pierre Neidhardt writes: >> 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. > My bad here, I should have been clearer in my explaination. The patched Qemu is not used during build but during runtime. From my understanding, it's provided as a way to start X applications under Arcan. The patch is probably just used to give qemu the ability to communicate with Arcan server. So using 'guix environment' might just be a good solution. (I wonder if it could be possible to user guix containers in the same way...) >> 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 sources? > > This happens a lot with other packages (e.g. the Go build system). The answer > 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. I'll look iton tis! ;) > Hope that helps! > Lprndn