From: Matt Rice <ratmice@gmail.com>
To: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
Cc: gdb@sourceware.org, Abdoulaye Walsimou GAYE <awg@embtoolkit.org>
Subject: Re: symlink old tarball name to new one
Date: Sat, 10 Sep 2011 23:00:00 -0000 [thread overview]
Message-ID: <CACTLOFq4Xo=gknUWHavVV5uud3=CymTn9sLL7_JZAswjHaSMXA@mail.gmail.com> (raw)
In-Reply-To: <201109110028.37733.yann.morin.1998@anciens.enib.fr>
On Sat, Sep 10, 2011 at 3:28 PM, Yann E. MORIN
<yann.morin.1998@anciens.enib.fr> wrote:
> As 'ratmice' said on IRC, this has a drawback for those tools that do check
> the tarballs using md5 (or sha1...). Using signatures is not an issue.
> But not all tools do use md5 (or even sigs).
FWIW, I'm not sure that this is much of an argument for tools that do
check using sums,
they have only one option... They must change their build script
regardless of the symlink.
further, the gdb ftp site doesn't host sums, so theres really nothing
to compare it to otherwise. (unless people are in the habit of
checking the gpg sig, making a sum and then checking that in which
case, they are in the 'they must change their script dept.).
anyhow, its something to consider and leaves a bitter taste in my
mouth, but i'm not objecting, it probably fixes more issues than it
causes.
next prev parent reply other threads:[~2011-09-10 23:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-01 9:51 was (Fwd: Re: binutils-2.20.1a replaced by 2.20.1 and so 2.21.1a?): " Abdoulaye Walsimou GAYE
2011-09-10 22:28 ` Yann E. MORIN
2011-09-10 23:00 ` Matt Rice [this message]
2011-09-10 23:27 ` Yann E. MORIN
2011-09-12 16:40 ` Joel Brobecker
2011-09-13 14:15 ` Yann E. MORIN
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='CACTLOFq4Xo=gknUWHavVV5uud3=CymTn9sLL7_JZAswjHaSMXA@mail.gmail.com' \
--to=ratmice@gmail.com \
--cc=awg@embtoolkit.org \
--cc=gdb@sourceware.org \
--cc=yann.morin.1998@anciens.enib.fr \
/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).