From: Mark Wielaard <mark@klomp.org>
To: Sasha Da Rocha Pinheiro <darochapinhe@wisc.edu>,
"elfutils-devel@sourceware.org" <elfutils-devel@sourceware.org>
Subject: Re: dependency
Date: Sat, 30 Jun 2018 01:25:00 -0000 [thread overview]
Message-ID: <1530321859.12946.198.camel@klomp.org> (raw)
In-Reply-To: <BN6PR06MB29324A714FBD9E45BA769058A64D0@BN6PR06MB2932.namprd06.prod.outlook.com>
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
next prev parent reply other threads:[~2018-06-30 1:25 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 ` Mark Wielaard [this message]
2018-07-02 22:04 ` dependency Sasha Da Rocha Pinheiro
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=1530321859.12946.198.camel@klomp.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).