From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Seeking advice: preparing releases on GuixSD. Date: Fri, 23 Dec 2016 13:35:04 +0000 Message-ID: <874m1uvkdz.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44651) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cKQ0P-0001K8-An for help-guix@gnu.org; Fri, 23 Dec 2016 08:35:30 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cKQ0K-0006QE-JE for help-guix@gnu.org; Fri, 23 Dec 2016 08:35:29 -0500 Received: from aibo.runbox.com ([91.220.196.211]:35898) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cKQ0K-0006Nl-BK for help-guix@gnu.org; Fri, 23 Dec 2016 08:35:24 -0500 Received: from [10.9.9.212] (helo=mailfront12.runbox.com) by bars.runbox.com with esmtp (Exim 4.71) (envelope-from ) id 1cKQ0I-00038i-Qr for help-guix@gnu.org; Fri, 23 Dec 2016 14:35:22 +0100 Received: from orion1626.startdedicated.com ([85.25.44.141] helo=localhost) by mailfront12.runbox.com with esmtpsa (uid:892961 ) (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) id 1cKPzk-0004lI-9G for help-guix@gnu.org; Fri, 23 Dec 2016 14:34:48 +0100 List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: help-guix@gnu.org Hi, my previous releases of gnurl (https://gnunet.org/gnurl) have been tested on Gentoo and GuixSD and prepared to release only on Gentoo, copied back to GuixSD and finished up on that GuixSD system. With my switch to GuixSD (and leaving Gentoo) 2 or 3 versions ago I have to advice people to run ./buildconf again (essentially: run autotools again), because of artifacts in shebangs and paths of generated files. I see three solutions right now: 1. Opt out of the ./buildconf part and make it a responsibility of users and distributions to run it. 2. Patch (adjust) maketgz, make dist, or any similar hook/script to my needs on GuixSD. 3. Simply remove all occurences of any /gnu/store/… (if it's that simple) which could also happen in (2). I hope I'm not the only person using GuixSD for releasing software. How do you all deal with these shebangs and paths? Thanks! -- ♥Ⓐ ng0 PGP keys and more: https://n0is.noblogs.org/ http://ng0.chaosnet.org