public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mark@klomp.org>
To: Sasha Da Rocha Pinheiro <darochapinhe@wisc.edu>
Cc: "elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
Subject: Re: dependency
Date: Wed, 04 Jul 2018 21:29:00 -0000	[thread overview]
Message-ID: <20180704212908.GD7556@wildebeest.org> (raw)
In-Reply-To: <BN6PR06MB29325898BC79DBA12AC5B39EA6430@BN6PR06MB2932.namprd06.prod.outlook.com>

[-- Attachment #1: Type: text/plain, Size: 932 bytes --]

On Mon, Jul 02, 2018 at 10:04:05PM +0000, Sasha Da Rocha Pinheiro wrote:
> I think the link should be direct to the file, since we download and
> extract. Otherwise, if the link was to a directory the issue would
> continue, since we would need to verify the version to compose the
> filename.
> 
> Now as for stable/latest/current, I don't have a preference. But I feel
> like it should be latest, since all elfutils releases are stable. 

OK, from now on https://sourceware.org/elfutils/ftp/elfutils-latest.tar.bz2
should point to the latest release.
And https://sourceware.org/elfutils/ftp/elfutils-latest.tar.bz2.sig to
the corresponding gpg signature for the tar.bz2.

See also the attached update to the elfutils-htdocs.

I also added an upload-release.sh script that can be run to create,
sign, upload and update the links (if you are a maintainer with a
sourceware shell account).

Thanks for the suggestion.

Cheers,

Mark

[-- Attachment #2: 0001-Add-last-release-and-signature-links.patch --]
[-- Type: text/x-diff, Size: 1013 bytes --]

From 954b1199737ca1047bc1bad82fcff6c3ce5ec2ec Mon Sep 17 00:00:00 2001
From: Mark Wielaard <mark@klomp.org>
Date: Wed, 4 Jul 2018 23:21:19 +0200
Subject: [PATCH] Add last release (and signature) links

---
 index.html | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 2e832ac..89449ce 100644
--- a/index.html
+++ b/index.html
@@ -54,7 +54,9 @@
       See the <A HREF="https://sourceware.org/git/?p=elfutils.git;a=blob_plain;f=CONTRIBUTING;hb=HEAD">CONTRIBUTING</A> file for how to propose patches to the code.
     </P>
 
-    <P>Releases:
+    <P>Last release: <A HREF="https://sourceware.org/elfutils/ftp/elfutils-latest.tar.bz2">tar.bz2</A> (<A HREF="https://sourceware.org/elfutils/ftp/elfutils-latest.tar.bz2.sig">sig</A>)</P>
+
+    <P>All releases:
       <A HREF="ftp://sourceware.org/pub/elfutils/">ftp://sourceware.org/pub/elfutils/</A> or <A HREF="https://sourceware.org/elfutils/ftp/">https://sourceware.org/elfutils/ftp/</A>
     </P>
 
-- 
2.18.0


[-- Attachment #3: 0001-config-Add-upload-release.sh-script.patch --]
[-- Type: text/x-diff, Size: 1952 bytes --]

From 45591ea8e54c4af4ae9a00ed85f22e09133e3dcf Mon Sep 17 00:00:00 2001
From: Mark Wielaard <mark@klomp.org>
Date: Wed, 4 Jul 2018 23:08:41 +0200
Subject: [PATCH] config: Add upload-release.sh script.

Should be run after making a release to upload the new tar.bz2,
signature file and update the latest symlinks. Make sure to run
make distcheck first. Requires a shell account on sourceware.

Signed-off-by: Mark Wielaard <mark@klomp.org>
---
 config/ChangeLog         |  4 ++++
 config/upload-release.sh | 31 +++++++++++++++++++++++++++++++
 2 files changed, 35 insertions(+)
 create mode 100755 config/upload-release.sh

diff --git a/config/ChangeLog b/config/ChangeLog
index 0e9cc28c..f281eb27 100644
--- a/config/ChangeLog
+++ b/config/ChangeLog
@@ -1,3 +1,7 @@
+2018-07-04  Mark Wielaard  <mark@klomp.org>
+
+	* upload-release.sh: New file.
+
 2018-06-11  Mark Wielaard  <mark@klomp.org>
 
 	* elfutils.spec.in: Update for 0.172.
diff --git a/config/upload-release.sh b/config/upload-release.sh
new file mode 100755
index 00000000..320d1ada
--- /dev/null
+++ b/config/upload-release.sh
@@ -0,0 +1,31 @@
+#!/bin/bash
+
+# Any error is fatal
+set -e
+
+# We take one arguent, the version (e.g. 0.173)
+if [ $# -ne 1 ]; then
+  echo "$0 <version> (e.g. 0.169)"
+  exit 1
+fi
+
+VERSION="$1"
+
+# Check we are in the build dir already configured.
+ELFUTILS_VERSION=$(echo $VERSION | cut -f2 -d\.)
+grep $ELFUTILS_VERSION version.h \
+	|| (echo "Must be run in configured build dir for $VERSION"; exit -1)
+
+make dist
+
+mkdir $VERSION
+cp elfutils-$VERSION.tar.bz2 $VERSION/
+cd $VERSION/
+gpg -b elfutils-$VERSION.tar.bz2
+cd ..
+scp -r $VERSION sourceware.org:/sourceware/ftp/pub/elfutils/
+
+ssh sourceware.org "(cd /sourceware/ftp/pub/elfutils \
+  && ln -sf $VERSION/elfutils-$VERSION.tar.bz2 elfutils-latest.tar.bz2 \
+  && ln -sf $VERSION/elfutils-$VERSION.tar.bz2.sig elfutils-latest.tar.bz2.sig \
+  && ls -lah elfutils-latest*)"
-- 
2.18.0


      reply	other threads:[~2018-07-04 21:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-30  0:50 dependency Sasha Da Rocha Pinheiro
2018-06-30  1:12 ` dependency Frank Ch. Eigler
2018-06-30  1:16   ` dependency Sasha Da Rocha Pinheiro
2018-06-30  1:25 ` dependency Mark Wielaard
2018-07-02 22:04   ` dependency Sasha Da Rocha Pinheiro
2018-07-04 21:29     ` Mark Wielaard [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180704212908.GD7556@wildebeest.org \
    --to=mark@klomp.org \
    --cc=darochapinhe@wisc.edu \
    --cc=elfutils-devel@sourceware.org \
    /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).