mirror of
git://gcc.gnu.org/git/gcc.git
synced 2025-02-21 06:19:15 +08:00
maintainer-scripts (snapshot_print): New function.
2004-08-03 Kelley Cook <kcook@gcc.gnu.org> * maintainer-scripts (snapshot_print): New function. (announce_snapshot): Generate announcment on the fly. Use a directory link for LATEST. * snapshot-README: Delete. * snapshot-index.html: Delete. From-SVN: r85508
This commit is contained in:
parent
3e558e8064
commit
2e84789689
@ -1,3 +1,11 @@
|
||||
2004-08-03 Kelley Cook <kcook@gcc.gnu.org>
|
||||
|
||||
* maintainer-scripts (snapshot_print): New function.
|
||||
(announce_snapshot): Generate announcment on the fly.
|
||||
Use a directory link for LATEST.
|
||||
* snapshot-README: Delete.
|
||||
* snapshot-index.html: Delete.
|
||||
|
||||
2004-06-09 Paolo Bonzini <bonzini@gnu.org>
|
||||
|
||||
* gcc_release (build_sources): Move the libcpp gmo files
|
||||
|
@ -407,36 +407,110 @@ upload_files() {
|
||||
done
|
||||
}
|
||||
|
||||
#Print description if snapshot exists
|
||||
snapshot_print() {
|
||||
if [ -e ${RELEASE}/${SNAP_FILE} ]; then
|
||||
printf "%-38s%s\n\n" "${SNAP_FILE}" "${SNAP_DESCRIPTION}" >> ${SNAPSHOT_README}
|
||||
echo -e " <tr><td><a href=\"${SNAP_FILE}\">${SNAP_FILE}</a></td>\n" \
|
||||
" <td>${SNAP_DESCRIPTION}</td></tr>" >> ${SNAPSHOT_INDEX}
|
||||
fi
|
||||
}
|
||||
|
||||
# Announce a snapshot, both on the web and via mail.
|
||||
announce_snapshot() {
|
||||
inform "Updating links and READMEs on the FTP server"
|
||||
|
||||
TEXT_DATE=`date --date=$DATE +%B\ %d,\ %Y`
|
||||
changedir "${SNAPSHOTS_DIR}"
|
||||
sed -e "s%@DATE@%$DATE%g" \
|
||||
-e "s%@TEXT_DATE@%$TEXT_DATE%g" \
|
||||
-e "s%@LAST_DATE@%$LAST_DATE%g" \
|
||||
-e "s%@BRANCH@%${BRANCH}%g" \
|
||||
-e "s%@RELEASE@%${RELEASE}%g" \
|
||||
-e "s%@EXPORT@%${EXPORTTAG} ${EXPORTDATE}%g" \
|
||||
~/scripts/snapshot-README > $$
|
||||
mv $$ ${RELEASE}/README
|
||||
sed -e "s%@DATE@%$DATE%g" \
|
||||
-e "s%@TEXT_DATE@%$TEXT_DATE%g" \
|
||||
-e "s%@LAST_DATE@%$LAST_DATE%g" \
|
||||
-e "s%@BRANCH@%${BRANCH}%g" \
|
||||
-e "s%@RELEASE@%${RELEASE}%g" \
|
||||
-e "s%@EXPORT@%${EXPORTTAG} ${EXPORTDATE}%g" \
|
||||
~/scripts/snapshot-index.html > $$
|
||||
mv $$ ${RELEASE}/index.html
|
||||
SNAPSHOT_README=${RELEASE}/README
|
||||
SNAPSHOT_INDEX=${RELEASE}/index.html
|
||||
|
||||
touch LATEST-IS-${BRANCH}-${DATE}
|
||||
rm -f LATEST-IS-${BRANCH}-${LAST_DATE}
|
||||
changedir "${SNAPSHOTS_DIR}"
|
||||
echo -e "Snapshot gcc-"${RELEASE}" is now available on" \
|
||||
"\n ftp://gcc.gnu.org/pub/gcc/snapshots/"${RELEASE}"/" \
|
||||
"\nand on various mirrors, see http://gcc.gnu.org/mirrors.html for details." \
|
||||
"\n\nThis snapshot has been generated from the GCC "${BRANCH}" CVS branch" \
|
||||
"\nwith the following options: "${EXPORTTAG} ${EXPORTDATE} \
|
||||
"\n\nYou'll find:\n" > ${SNAPSHOT_README}
|
||||
|
||||
echo -e "<html>" \
|
||||
"\n\n<head>" \
|
||||
"\n<title>GCC "${RELEASE}" Snapshot</title>" \
|
||||
"\n</head>" \
|
||||
"\n\n<body>" \
|
||||
"\n<h1>GCC "${RELEASE}" Snapshot</h1>" \
|
||||
"\n\n<p>The <a href =\"http://gcc.gnu.org/\">GCC Project</a> makes" \
|
||||
"\nperiodic snapshots of the GCC source tree available to the public" \
|
||||
"\nfor testing purposes.</p>" \
|
||||
"\n\n<p>If you are planning to download and use one of our snapshots, then" \
|
||||
"\nwe highly recommend you join the GCC developers list. Details for" \
|
||||
"\nhow to sign up can be found on the GCC project home page.</p>" \
|
||||
"\n\n<p>This snapshot has been generated from the GCC "${BRANCH}" CVS branch" \
|
||||
"\nwith the following options: <code>"${EXPORTTAG} ${EXPORTDATE}"</code></p>" \
|
||||
"\n\n<table>" > ${SNAPSHOT_INDEX}
|
||||
|
||||
SNAP_FILE=gcc-${RELEASE}.tar.bz2
|
||||
SNAP_DESCRIPTION="Complete GCC (includes all of below)"
|
||||
snapshot_print
|
||||
|
||||
SNAP_FILE=gcc-core-${RELEASE}.tar.bz2
|
||||
SNAP_DESCRIPTION="C front end and core compiler"
|
||||
snapshot_print
|
||||
|
||||
SNAP_FILE=gcc-ada-${RELEASE}.tar.bz2
|
||||
SNAP_DESCRIPTION="Ada front end and runtime"
|
||||
snapshot_print
|
||||
|
||||
SNAP_FILE=gcc-fortran-${RELEASE}.tar.bz2
|
||||
SNAP_DESCRIPTION="Fortran front end and runtime"
|
||||
snapshot_print
|
||||
|
||||
SNAP_FILE=gcc-g++-${RELEASE}.tar.bz2
|
||||
SNAP_DESCRIPTION="C++ front end and runtime"
|
||||
snapshot_print
|
||||
|
||||
SNAP_FILE=gcc-g77-${RELEASE}.tar.bz2
|
||||
SNAP_DESCRIPTION="Fortran 77 front end and runtime"
|
||||
snapshot_print
|
||||
|
||||
SNAP_FILE=gcc-java-${RELEASE}.tar.bz2
|
||||
SNAP_DESCRIPTION="Objective-C front end and runtime"
|
||||
snapshot_print
|
||||
|
||||
SNAP_FILE=gcc-objc-${RELEASE}.tar.bz2
|
||||
SNAP_DESCRIPTION="Java front end and runtime"
|
||||
snapshot_print
|
||||
|
||||
SNAP_FILE=gcc-testsuite-${RELEASE}.tar.bz2
|
||||
SNAP_DESCRIPTION="The GCC testsuite"
|
||||
snapshot_print
|
||||
|
||||
echo -e "\nDiffs from "${BRANCH}"-"${LAST_DATE}" are available in the diffs/ subdirectory." \
|
||||
"\n\nWhen a particular snapshot is ready for public consumption the LATEST-"${BRANCH} \
|
||||
"\nlink is updated and a message is sent to the gcc list. Please do not use" \
|
||||
"\na snapshot before it has been announced that way." >> ${SNAPSHOT_README}
|
||||
|
||||
echo -e "</table>" \
|
||||
"\n<p>Diffs from "${BRANCH}"-"${LAST_DATE}" are available in the" \
|
||||
"\n<a href=\"diffs/\">diffs/ subdirectory</a>.</p>" \
|
||||
"\n\n<p>When a particular snapshot is ready for public consumption the LATEST-"${BRANCH} \
|
||||
"\nlink is updated and a message is sent to the gcc list. Please do not use" \
|
||||
"\na snapshot before it has been announced that way.</p>" \
|
||||
"\n\n<hr />" \
|
||||
"\n\n<address>" \
|
||||
"\n<a href=\"mailto:gcc@gcc.gnu.org\">gcc@gcc.gnu.org</a>" \
|
||||
"\n<br />" \
|
||||
"\nLast modified "${TEXT_DATE} \
|
||||
"\n</address>" \
|
||||
"\n</body>" \
|
||||
"\n\n</html>" >> ${SNAPSHOT_INDEX}
|
||||
|
||||
rm -f LATEST-${BRANCH}
|
||||
ln -s ${RELEASE} LATEST-${BRANCH}
|
||||
|
||||
inform "Sending mail"
|
||||
|
||||
export QMAILHOST=gcc.gnu.org
|
||||
mail -s "gcc-ss-${RELEASE} is now available" gcc@gcc.gnu.org < ${SNAPSHOTS_DIR}/${RELEASE}/README
|
||||
mail -s "gcc-${RELEASE} is now available" gcc@gcc.gnu.org < ${SNAPSHOT_README}
|
||||
}
|
||||
|
||||
########################################################################
|
||||
|
@ -1,34 +0,0 @@
|
||||
gcc-ss-@RELEASE@ is now available on
|
||||
ftp://gcc.gnu.org/pub/gcc/snapshots/@RELEASE@/
|
||||
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
|
||||
|
||||
This snapshot has been generated from the GCC @BRANCH@ CVS branch
|
||||
with the following options: @EXPORT@
|
||||
|
||||
You'll find:
|
||||
|
||||
gcc-@RELEASE@.tar.bz2 The full GCC snapshot, including all
|
||||
languages and runtime libraries.
|
||||
|
||||
gcc-core-@RELEASE@.tar.bz2 Just the C front end and core compiler.
|
||||
|
||||
gcc-testsuite-@RELEASE@.tar.bz2 The GCC testsuite.
|
||||
|
||||
gcc-ada-@RELEASE@.tar.bz2 The Ada language and runtime.
|
||||
|
||||
gcc-g++-@RELEASE@.tar.bz2 The C++ front end and runtime.
|
||||
|
||||
gcc-g77-@RELEASE@.tar.bz2 The F77 front end and runtime.
|
||||
|
||||
gcc-fortran-@RELEASE@.tar.gz The Fortran front end and runtime.
|
||||
|
||||
gcc-objc-@RELEASE@.tar.bz2 The Objective-C front end and runtime.
|
||||
|
||||
gcc-java-@RELEASE@.tar.bz2 The Java front end and runtime.
|
||||
|
||||
Diffs from @BRANCH@-@LAST_DATE@ are available in the diffs/ subdirectory.
|
||||
|
||||
|
||||
When a particular snapshot is ready for public consumption the LATEST-IS-
|
||||
file is updated and a message is sent to the gcc list. Please do not use
|
||||
a snapshot before it has been announced that way.
|
@ -1,71 +0,0 @@
|
||||
<html>
|
||||
|
||||
<head>
|
||||
<title>GCC @RELEASE@ Snapshot</title>
|
||||
</head>
|
||||
|
||||
<body>
|
||||
<h1>GCC @RELEASE@ Snapshot</h1>
|
||||
|
||||
<p>The <a href ="http://gcc.gnu.org/">GCC Project</a> makes
|
||||
periodic snapshots of the GCC source tree available to the public
|
||||
for testing purposes.</p>
|
||||
|
||||
<p>If you are planning to download and use one of our snapshots, then
|
||||
we highly recommend you join the GCC developers list. Details for
|
||||
how to sign up can be found on the GCC project home page.</p>
|
||||
|
||||
<p>This snapshot has been generated from the GCC @BRANCH@ CVS branch
|
||||
with the following options: @EXPORT@</p>
|
||||
|
||||
<blockquote>
|
||||
<p> <a href="gcc-@RELEASE@.tar.bz2">
|
||||
gcc</a> @TEXT_DATE@ snapshot, includes all languages.
|
||||
|
||||
<p> <a href="gcc-core-@RELEASE@.tar.bz2">
|
||||
gcc-core</a> @TEXT_DATE@ snapshot, includes just the C front
|
||||
end and core compiler.
|
||||
|
||||
<p> <a href="gcc-g++-@RELEASE@.tar.bz2">
|
||||
gcc-g++</a> @TEXT_DATE@ snapshot, includes just the C++ front
|
||||
end and runtime.
|
||||
|
||||
<p> <a href="gcc-g77-@RELEASE@.tar.bz2">
|
||||
gcc-g77</a> @TEXT_DATE@ snapshot, includes just the F77 front
|
||||
end and runtime.
|
||||
|
||||
<p> <a href="gcc-fortran-@RELEASE@.tar.bz2">
|
||||
gcc-fortran</a> @TEXT_DATE@ snapshot, includes just the Fortran front
|
||||
end and runtime.
|
||||
|
||||
<p> <a href="gcc-java-@RELEASE@.tar.bz2">
|
||||
gcc-java</a> @TEXT_DATE@ snapshot, includes just the Java
|
||||
front end and runtime.
|
||||
|
||||
<p> <a href="gcc-objc-@RELEASE@.tar.bz2">
|
||||
gcc-objc</a> @TEXT_DATE@ snapshot, includes just the Objective-C
|
||||
front end and runtime.
|
||||
|
||||
<p> <a href="gcc-ada-@RELEASE@.tar.bz2">
|
||||
gcc-ada</a> @TEXT_DATE@ snapshot, includes just the Ada
|
||||
front end and runtime.
|
||||
|
||||
</blockquote>
|
||||
|
||||
<p>Diffs from @BRANCH@-@LAST_DATE@ are available in the
|
||||
<a href="diffs/">diffs/ subdirectory</a>.</p>
|
||||
|
||||
</p>When a particular snapshot is ready for public consumption the LATEST-IS-
|
||||
file is updated and a message is sent to the gcc list. Please do not use
|
||||
a snapshot before it has been announced that way.</p>
|
||||
|
||||
<hr />
|
||||
|
||||
<address>
|
||||
<a href="mailto:gcc@gcc.gnu.org">gcc@gcc.gnu.org</a>
|
||||
<br />
|
||||
Last modified @TEXT_DATE@
|
||||
</address>
|
||||
</body>
|
||||
|
||||
</html>
|
Loading…
Reference in New Issue
Block a user