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. > 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. -- Alex