Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Yann E. MORIN" <yann.morin.1998@anciens.enib.fr>
To: gdb@sourceware.org
Cc: Abdoulaye Walsimou GAYE <awg@embtoolkit.org>
Subject: Re: symlink old tarball name to new one
Date: Sat, 10 Sep 2011 22:28:00 -0000	[thread overview]
Message-ID: <201109110028.37733.yann.morin.1998@anciens.enib.fr> (raw)
In-Reply-To: <4E5F55A9.6080901@embtoolkit.org>

All,

Recently, the gdb release tarballs were re-released to fix the GPL
compliance issue with the cgen files. That's fine so far.

What's problematic is that the old tarballs were deleted, and new tarballs
were cretaed with an alternate name. This poses two problems.


First, autobuilders such as crosstool-NG or buildroot (but also many others)
that need to download the gdb sources now choke on the missing /legacy/
versions. This is an issue, because existing releases of these tools are
broken.


Second, the new tarballs were created with an 'a' appended to the version
string, making for example '7.1' being called in fact '7.1a', but the
directory within those tarballs are still named after the real version, in
this case '7.1'. So it is not possible to easily derive the tarball name
from the version string, and then the directory name from the tarball name.

Either we use an 'a' at the end of the version, and we can get the tarball
but we don't know the directory name; or we ignore the 'a', so we know the
directory name, but can't find the tarball.


On Thursday 01 September 2011 11:51:37 Abdoulaye Walsimou GAYE wrote:
> How about to have the same simlinks  to new gdb tarballs name?

I second Abdoulaye's suggestion.

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).

Providing legacy symlinks that point back to the new releases (for example
gdb-7.1.tar.bz2 points to gdb-7.1a.tar.bz2, ditto for .sig) would be a great
help for those projects.

For information, the binutils guys did agree to have those /legacy/ symlinks
put in place for binutils (which was Abdoulaye's initial forwarded message):
  http://sourceware.org/ml/binutils/2011-09/msg00000.html

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'


  reply	other threads:[~2011-09-10 22:28 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 [this message]
2011-09-10 23:00   ` Matt Rice
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=201109110028.37733.yann.morin.1998@anciens.enib.fr \
    --to=yann.morin.1998@anciens.enib.fr \
    --cc=awg@embtoolkit.org \
    --cc=gdb@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