Sasha Da Rocha Pinheiro
Mon Jul 2 22:04:00 GMT 2018

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.


From: Mark Wielaard <>
Sent: Friday, June 29, 2018 8:24 PM
To: Sasha Da Rocha Pinheiro;
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?

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

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?



More information about the Elfutils-devel mailing list