From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21163 invoked by alias); 10 Sep 2011 22:28:57 -0000 Received: (qmail 21151 invoked by uid 22791); 10 Sep 2011 22:28:55 -0000 X-SWARE-Spam-Status: No, hits=-0.6 required=5.0 tests=AWL,BAYES_40,RCVD_IN_DNSWL_NONE X-Spam-Check-By: sourceware.org Received: from smtp04.smtpout.orange.fr (HELO smtp.smtpout.orange.fr) (80.12.242.126) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 10 Sep 2011 22:28:41 +0000 Received: from treguer.localnet ([90.32.170.148]) by mwinf5d08 with ME id XAUf1h0013CT72q03AUfJG; Sun, 11 Sep 2011 00:28:39 +0200 X-ME-engine: default From: "Yann E. MORIN" To: gdb@sourceware.org Subject: Re: symlink old tarball name to new one Date: Sat, 10 Sep 2011 22:28:00 -0000 User-Agent: KMail/1.13.5 (Linux/3.0.4-treguer; KDE/4.4.5; x86_64; ; ) Cc: Abdoulaye Walsimou GAYE References: <4E5F55A9.6080901@embtoolkit.org> In-Reply-To: <4E5F55A9.6080901@embtoolkit.org> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201109110028.37733.yann.morin.1998@anciens.enib.fr> Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-09/txt/msg00030.txt.bz2 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. | '------------------------------^-------^------------------^--------------------'