From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: Seeking advice: preparing releases on GuixSD. Date: Fri, 23 Dec 2016 17:34:11 +0000 Message-ID: <87bmw2tur0.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> References: <874m1uvkdz.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> <87pokishk6.fsf@gmail.com> 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]:36085) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cKTjJ-0001n7-K1 for help-guix@gnu.org; Fri, 23 Dec 2016 12:34:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cKTjE-0002ix-I3 for help-guix@gnu.org; Fri, 23 Dec 2016 12:34:05 -0500 Received: from aibo.runbox.com ([91.220.196.211]:57078) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cKTjE-0002i7-BF for help-guix@gnu.org; Fri, 23 Dec 2016 12:34:00 -0500 Received: from [10.9.9.210] (helo=mailfront10.runbox.com) by bars.runbox.com with esmtp (Exim 4.71) (envelope-from ) id 1cKTjB-0002z2-UB for help-guix@gnu.org; Fri, 23 Dec 2016 18:33:58 +0100 Received: from [162.220.246.230] (helo=localhost) by mailfront10.runbox.com with esmtpsa (uid:892961 ) (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) id 1cKTj9-0003Tu-4u for help-guix@gnu.org; Fri, 23 Dec 2016 18:33:55 +0100 In-Reply-To: <87pokishk6.fsf@gmail.com> 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 Alex Kost writes: > ng0 (2016-12-23 13:35 +0000) wrote: > >> 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. > > Do you mean "configure" and "Makefile.in" files? I don't see any > "/gnu/store" artifacts, if that's what you mean. Almost. What I mean is "Makefile", "configure", etc, everything which is left when you have run the ./buildconf, configure, make, make clean. For the current release this gave me too many /gnu/store/… lines, last release was better. I'm still trying to get away from the manual release plan I was given by the person who did the releases before me. >> 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? > > I made releases on GuixSD multiple times, but I've never faced the > problem you describe: "make dist" prepares system-independent files > without any artifacts AFAICT. This depends on how your make dist is written doesn't it? make dist is currently not completely functional here (or I need to investigate if the failures are actually false ones) and the "maketgz" script breaks because some binaries are not at /bin/* and needs to be adjusted to gnurl needs as far as I know. So far it was very manual what I did. > -- > Alex > -- ♥Ⓐ ng0 PGP keys and more: https://n0is.noblogs.org/ http://ng0.chaosnet.org