[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Seeking advice: preparing releases on GuixSD.

From: ng0
Subject: Re: Seeking advice: preparing releases on GuixSD.
Date: Fri, 23 Dec 2016 17:34:11 +0000

Alex Kost <address@hidden> writes:

> ng0 (2016-12-23 13:35 +0000) wrote:
>> Hi,
>> my previous releases of 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 "" 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:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]