dependency

dependency

[Sasha Da Rocha Pinheiro]

Hi,
is there a reference for the last stable version of Elfutils? 

Currently we set the following path in our cmake configuration to download and compile Elfutils as a dependency for Dyninst, but lately there has been some important modifications, and I think it would be nice to have a reference to a stable version so we don't need to check for new versions and update our make files.

https://sourceware.org/elfutils/ftp/0.168/elfutils-0.168.tar.bz2


Sasha

Re: dependency

[Frank Ch. Eigler]

Hi -

> is there a reference for the last stable version of Elfutils? 
> [...]
> https://sourceware.org/elfutils/ftp/0.168/elfutils-0.168.tar.bz2

Each elfutils release is "stable".  Are you looking for
a fixed URL for the most recent release?


- FChE

Re: dependency

[Sasha Da Rocha Pinheiro]

> Each elfutils release is "stable".  Are you looking for
> a fixed URL for the most recent release?

Yes, that's what I meant.

Sasha

 
From: Frank Ch. Eigler <fche@redhat.com>
Sent: Friday, June 29, 2018 8:12 PM
To: Sasha Da Rocha Pinheiro
Cc: elfutils-devel@sourceware.org
Subject: Re: dependency
  

Hi -

> is there a reference for the last stable version of Elfutils? 
> [...]
> https://sourceware.org/elfutils/ftp/0.168/elfutils-0.168.tar.bz2

Each elfutils release is "stable".  Are you looking for
a fixed URL for the most recent release?


- FChE
    

Re: dependency

[Mark Wielaard]

On Sat, 2018-06-30 at 00:49 +0000, Sasha Da Rocha Pinheiro wrote:
> Hi,
> is there a reference for the last stable version of Elfutils? 
> 
> Currently we set the following path in our cmake configuration to
> download and compile Elfutils as a dependency for Dyninst, but lately
> there has been some important modifications, and I think it would be
> nice to have a reference to a stable version so we don't need to
> check for new versions and update our make files.

We could certainly add some symlink(s) to the "latest" stable/released
version that is updated whenever we do a release.

What kind of naming/link is the most convenient?

Should it just be a link to the latest release dir?
https://sourceware.org/elfutils/ftp/latest/
-> https://sourceware.org/elfutils/ftp/0.172/

Or would a direct link to the source tar ball and signature file be
better?

https://sourceware.org/elfutils/ftp/latest/elfutils-latest.tar.bz2
-> https://sourceware.org/elfutils/ftp/0.172/elfutils-0.172.tar.bz2
https://sourceware.org/elfutils/ftp/latest/elfutils-latest.tar.bz2.sig
-> https://sourceware.org/elfutils/ftp/0.172/elfutils-0.172.tar.bz2.sig

Or some other scheme?

We could also have the buildbot create a "latest" or "current" from git
once all builds are green for example.

Which brings up the question, should we use "stable", "current" or
"latest" as link name, or is there a better, more standard name to use
for that? What do other projects use?

Thanks,

Mark

Re: dependency

[Sasha Da Rocha Pinheiro]

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. 

In Dyninst we use git branches, and we define which one is the latest stable in the README, but the master branch will have the latest implementations, which eventually will become a release.

Sasha


 
From: Mark Wielaard <mark@klomp.org>
Sent: Friday, June 29, 2018 8:24 PM
To: Sasha Da Rocha Pinheiro; elfutils-devel@sourceware.org
Subject: Re: dependency
  

On Sat, 2018-06-30 at 00:49 +0000, Sasha Da Rocha Pinheiro wrote:
> Hi,
> is there a reference for the last stable version of Elfutils? 
> 
> Currently we set the following path in our cmake configuration to
> download and compile Elfutils as a dependency for Dyninst, but lately
> there has been some important modifications, and I think it would be
> nice to have a reference to a stable version so we don't need to
> check for new versions and update our make files.

We could certainly add some symlink(s) to the "latest" stable/released
version that is updated whenever we do a release.

What kind of naming/link is the most convenient?

Should it just be a link to the latest release dir?
https://sourceware.org/elfutils/ftp/latest/
-> https://sourceware.org/elfutils/ftp/0.172/

Or would a direct link to the source tar ball and signature file be
better?

https://sourceware.org/elfutils/ftp/latest/elfutils-latest.tar.bz2
-> https://sourceware.org/elfutils/ftp/0.172/elfutils-0.172.tar.bz2
https://sourceware.org/elfutils/ftp/latest/elfutils-latest.tar.bz2.sig
->  https://sourceware.org/elfutils/ftp/0.172/elfutils-0.172.tar.bz2.sig

Or some other scheme?

We could also have the buildbot create a "latest" or "current" from git
once all builds are green for example.

Which brings up the question, should we use "stable", "current" or
"latest" as link name, or is there a better, more standard name to use
for that? What do other projects use?

Thanks,

Mark
    

Re: dependency

[Mark Wielaard]

[-- 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