This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Snapshots
- To: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Subject: Re: Snapshots
- From: "Joseph S. Myers" <jsm28 at cam dot ac dot uk>
- Date: Fri, 9 Mar 2001 15:08:39 +0000 (GMT)
- cc: Jeffrey A Law <law at redhat dot com>, <gcc at gcc dot gnu dot org>
On Thu, 8 Mar 2001, Gerald Pfeifer wrote:
> Okay, so here are some details: The gccadmin account has been generated
> is already being used for snapshots etc (IIRC). It can be accessed by
> various SC members (Mark Mitchell,...), root folks on gcc.gnu.org (Tom
> Tromey, Chris Faylor, myself), plus you (sic!).
Where does mail to gccadmin (generated by cron jobs, etc.) end up?
Does gccadmin have write access to the ftp site?
Is it appropriate for cron jobs on gcc.gnu.org to check out and configure
(but not build) a source tree? (For some purposes - regenerating files
such as gcc.pot which should be regenerated every so often but don't need
to be with every commit - it seems better to me to use the existing
Makefile rules rather than duplicating them in scripts - which requires
configuring a source tree. The same applies to the inclusion of info and
Bison output files in release tarballs.)
What's the appropriate (local to gcc.gnu.org) time of day for cron jobs to
run at?
Should requests for software to be installed for such cron jobs (e.g. CVS
gettext for regenerating gcc.pot, podlators for regenerating manpages) go
to overseers, or should I install them under gccadmin's home directory?
Should I just go ahead and test and set up cron jobs for this sort of
thing, then send them to gcc-patches and commit them to a
maintainer-scripts directory, or should scripts run from cron be approved
in advance?
--
Joseph S. Myers
jsm28@cam.ac.uk