This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [gcc_release] Generate release/snapshot announcements on thefly
- From: Gerald Pfeifer <gerald at pfeifer dot com>
- To: Kelley Cook <kcook at gcc dot gnu dot org>
- Cc: GCC Patches <gcc-patches at gcc dot gnu dot org>,"Joseph S. Myers" <jsm at polyomino dot org dot uk>,Toon Moene <toon at moene dot indiv dot nluug dot nl>
- Date: Wed, 4 Aug 2004 10:09:05 +0200 (CEST)
- Subject: Re: [gcc_release] Generate release/snapshot announcements on thefly
- References: <20040801175748.29753.qmail@sourceware.org><410D3A43.6080104@moene.indiv.nluug.nl> <410EB8E3.1040600@gcc.gnu.org>
On Mon, 2 Aug 2004, Kelley Cook wrote:
Cavaets: It requires an echo that recognizes the non-posix "-e" switch so I
can output newlines.
I recommend using printf instead, or, simpler to maintain, a here
document (the bash man page has a nice description of these).
Instead of
SNAP_FILE=gcc-g77-${RELEASE}.tar.bz2
SNAP_DESCRIPTION="Fortran 77 front end and runtime"
snapshot_print
I'd prefer
snapshot_print gcc-g77-${RELEASE}.tar.bz2 \
"Fortran 77 front end and runtime"
and than using $1 and $2 in that function.
In addition it changes the currently blank file LATEST-IS-3.5-20040802 to be
a symbolic link LATEST-3.5 pointing to the proper directory. I think this is
a good change, but for cleanup it will require the manual removal of the
currently generated LATEST* files.
I just updated the copy of the script running on gcc.gnu.org, so we'll see
it at work starting today; I'll take care of the old LATEST* files then.
Tested as best I could with a cobbled together ftp/snapshots directory.
Generated README looks good.
Generated index.html passes validator.org
Thanks!
Gerald