From: ng0 <ng0@libertad.pw>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org
Subject: Re: Seeking advice: preparing releases on GuixSD.
Date: Sat, 24 Dec 2016 16:34:55 +0000 [thread overview]
Message-ID: <874m1tp9ow.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87vau9nvnf.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> ng0 <ng0@libertad.pw> writes:
>
>> Ricardo Wurmus <rekado@elephly.net> writes:
>>
>>> ng0 <ng0@libertad.pw> writes:
>>>
>>>> Ricardo Wurmus <rekado@elephly.net> writes:
>>>>
>>>>> What I get is a tarball named “gnurl--.tar.gz” (because “configure.ac”
>>>>> specifies the version as a dash). Unpacking it I see exactly *one*
>>>>> reference to something in /gnu/store and that’s in “ltmain.sh”.
>>>>
>>>> Hm.. that's what I had too before I asked here, I just felt there
>>>> must be 0 occurences of /gnu/store.
>>>
>>> You wrote earlier:
>>>
>>>> 3. Simply remove all occurences of any /gnu/store/… (if it's
>>>> that simple) which could also happen in (2).
>>>
>>> That made it sound like there are countless references that need to be
>>> corrected somehow.
>>
>> Well in 7.52.0 there are more than 1 reference to /gnu/store, and
>> in 7.52.1 there were more than in 7.52.0 simply because I did not
>> have the time to investigate what's wrong now.
>
> If you did what I did on GuixSD (exact sequence in my previous email) I
> don’t see how there could have been any more references to store items.
More or less, the tl;dr of updates right now is:
old=7_50_1
new=7_50_2
git checkout upstream/master; git pull; git checkout -b gnurl-$new curl-$new # tag of desired version
git cherry-pick `git log gnurl-$old | head -n 1 | cut -c8-`
git mergetool # or whatever needs to be used to fix the broken ones
git cherry-pick --continue
# run the guix-gnurl.scm to test.
./buildconf
./configure --enable-ipv6 --with-gnutls --without-libssh2 --without-libmetalink \
--without-winidn --without-librtmp --without-nghttp2 --without-nss --without-cyassl \
--without-polarssl --without-ssl --without-winssl --without-darwinssl --disable-sspi \
--disable-ntlm-wb --disable-ldap --disable-rtsp --disable-dict --disable-telnet --disable-tftp \
--disable-pop3 --disable-imap --disable-smtp --disable-gopher \
--disable-file --disable-ftp --disable-smb
make
make clean
git push -f origin gnurl-$new:master
git diff HEAD^ HEAD >..&gnurl-$new.diff
cp -a . ../gnurl-$new
cd ..
rm -rf gnurl-$new/.git
tar cjf gnurl-$new.tar.bz2 gnurl-$new
rm -rf gnurl-$new
gpg --detach-sig gnurl-$new.tar.bz2
# login to gnunet.org and upload them
Where some parts of this manual procedure have been changed now.
I'll try a simple `make dist` next time.
I will compare my nroff or whatever it was called package with
yours and see if there's anything left to add, if you think it
should go into guix, it's good for me.
>>> “ltmain.sh” is instantiated from a template by libtool. It originally
>>> contains a /bin/sh shebang, and I think it should not be patched when
>>> installed to
>>
>> So I can assume that just changing the shebang in ltmain.sh back
>> to /bin/sh is enough to make it distributable again, or is
>> ltmain.sh something distributions have anyway and the local file
>> is "just there"?
>
> ltmain.sh is included by “make dist”, so it’s supposed to be
> distributed. One of the big ideas of autotools is that users don’t have
> to have autotools to build a release tarball.
>
> --
> Ricardo
>
> GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
> http://elephly.net
>
>
So the changed shebang in the ltmain.sh is a bug on my side or in
the autotools in Guix? I'm not looking at the sources right now,
but I think I could simply add a line (for make dist) which
changes the shebang back to /bin/sh before assembling the
tarball. After all it's just a shebang.
--
♥Ⓐ ng0
PGP keys and more: https://n0is.noblogs.org/ http://ng0.chaosnet.org
next prev parent reply other threads:[~2016-12-24 16:35 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 13:35 Seeking advice: preparing releases on GuixSD ng0
2016-12-23 17:04 ` Alex Kost
2016-12-23 17:34 ` ng0
2016-12-24 10:13 ` Ricardo Wurmus
2016-12-24 14:45 ` ng0
2016-12-24 15:32 ` Ricardo Wurmus
2016-12-24 16:13 ` ng0
2016-12-24 16:23 ` Ricardo Wurmus
2016-12-24 16:34 ` ng0 [this message]
2016-12-26 13:58 ` Ricardo Wurmus
2016-12-26 14:27 ` ng0
2016-12-30 23:34 ` Ludovic Courtès
2016-12-24 22:26 ` ng0
2016-12-25 12:37 ` Ricardo Wurmus
2016-12-26 12:41 ` ng0
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874m1tp9ow.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me \
--to=ng0@libertad.pw \
--cc=help-guix@gnu.org \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).