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

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
    

  reply	other threads:[~2018-07-02 22:04 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   ` Sasha Da Rocha Pinheiro [this message]
2018-07-04 21:29     ` dependency Mark Wielaard

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=BN6PR06MB29325898BC79DBA12AC5B39EA6430@BN6PR06MB2932.namprd06.prod.outlook.com \
    --to=darochapinhe@wisc.edu \
    --cc=elfutils-devel@sourceware.org \
    --cc=mark@klomp.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).