GCC 3.0 Release Criteria

[Philipp Thomas]

* Zack Weinberg (zack@wolery.cumb.org) [20000430 20:40]:

> Would you mind arranging to have the various files generated in the po
> subdir be created in the build tree?

Not at all, as I too believe they should be generated in the build tree :)
I'll try to come up with something. But as I will be on the road for the
next week (SuSE Roadshow :), it will be some time 'till I post it.

> Except maybe gcc.pot, which should probably be checked into CVS.

I don't think so, as if this is done, it would have to be regenerated with
every checkin that either modifies one of the files listed in po/POTFILES or
changes the list in POTFILES itself. For snapshots and releases we would of
cause have to generate it (along with the compiled catalogs), but for CVS
it's IMO not worth the trouble.

Whoever wants to use the NLS support already needs the library support and
the gettext utils. And now having the support enabled by default will
hopefully make compilation break much earlier when somebody does code
changes but forgets to update po/POTFILES.in.

BTW, Mark, IMO it would make sense to include the contents of
gcc/ABOUT-GCC-NLS in the gcc.info, now that we default to on. If
you agree, I'll do that and send in the patch.

Philipp

-- 
Philipp Thomas <pthomas@suse.de>
Development, SuSE GmbH, Schanzaecker Str. 10, D-90443 Nuremberg, Germany