RFC: Make gcc_release update the .pot file

[Joseph S. Myers]

On Wed, 13 Feb 2002, Zack Weinberg wrote:

> On Wed, Feb 13, 2002 at 10:49:55PM +0000, Joseph S. Myers wrote:
> > 
> > We were previously told
> > <URL:http://gcc.gnu.org/ml/gcc-patches/2001-12/msg00258.html> that
> > automatic .pot submission for snapshots was not wanted.
> 
> However, I suspect that if it isn't automated we'll reliably forget
> about it.  For instance, the current .pot file has serious problems
> with the Fortran messages being mistaken for printf strings, and we
> haven't uploaded a new one despite the fix being available for two
> weeks already.  I've had a couple messages from translators asking
> for a fresh .pot; I could do it by hand but I'd prefer to have a real
> procedure in place.

If automating overloads the translators and means they then don't have the
time to actually do the translations, then it won't help.

> Unfortunately, the tree has to be checked out and configured before we
> can regenerate the .pot file.  How about I just apply the tag to the
> new .pot file after checking it in?

For releases, the tree is checked out (cvs co), has ChangeLogs and version
files updated for the release and checked in, then the checked out source
tree is deleted.  After this, for releases and snapshots, the tag is
applied then the tree is exported (cvs export) from the tag.  For
generating the .pot file, the first checkout should be made unconditional
(applying for snapshots as well as releases), and the .pot regeneration
done on that checked out tree.

-- 
Joseph S. Myers
jsm28@cam.ac.uk