This is the mail archive of the
mailing list for the GCC project.
Re: Why is gcc-3.3.3 in a strange directory on ftp.gnu.org?
- From: Gabriel Dos Reis <gdr at integrable-solutions dot net>
- To: Jim Wilson <wilson at specifixinc dot com>
- Cc: Dan Kegel <dank at kegel dot com>, gcc at gcc dot gnu dot org
- Date: 17 May 2004 05:50:11 +0200
- Subject: Re: Why is gcc-3.3.3 in a strange directory on ftp.gnu.org?
- Organization: Integrable Solutions
- References: <40A4AD87.firstname.lastname@example.org> <40A8240D.email@example.com>
Jim Wilson <firstname.lastname@example.org> writes:
| Dan Kegel wrote:
| > Why is
| > ftp://ftp.gnu.org/pub/gnu/gcc/releases/gcc-3.3.3
| > in a different place than all the other releases on that site?
The summary is that the directory structure for gcc on
ftp.gnu.org is just inconsistent even if you disregard releases/.
Things should be simpler if the structure reflected that on our ftp
| We don't directly control the FSF ftp.gnu.org site. So this would
| have to be discussed with FSF sysadmins. I am not even sure who is
| the right person to contact.
The way directories now get created on ftp.gnu.org is probably clearer
than the way they get deleted. But that would imply keysigning at a
different date than when the original tarballs finally got there.
| I recall that there were problems getting gcc-3.3.3 uploaded to the
| FSF ftp site when it came out. We had a new release manager who had
| never done this before, and at roughly the same time the FSF changed
| their upload process because of yet another security problem. The
| result was a lot of confusion.
The problems were less with being my "first" time than how the
files were supposed to be uploaded and when they finally end up. One
can now argue after the fact how it should have been done :-)
Before, nobody really knew the right structure. (Even now, it is not
absolutely clear, look at gcc-3.4.0.tar.gz for example).
And the problem with getting the files uploaded on ftp.gnu.org was
due to an interesting bug in FSF's script to transfer the files.
| I suspect what happened is a little too literal copying from the
| gcc.gnu.org site. If you use ftp to conenct to gcc.gnu.org, then all
| gcc releases are in pub/gcc/releases. This happens to be where the
| release ended up on ftp.gnu.org, but the directory structure on
| ftp.gnu.org is a bit different, and it should have gone into just gcc
| instead of gcc/releases.