Buy GNU books!
|[ < ]||[ > ]||[ << ]||[ Up ]||[ >> ]||[Top]||[Contents]||[Index]||[ ? ]|
In a project development with multiple developers, using CVS, there
should be a single developer who occasionally - when there is desire to
upgrade to a new
gettext version - runs
performs the changes listed in 12.4 Files You Must Create or Alter, and then commits
his changes to the CVS.
It is highly recommended that all developers on a project use the same
version of GNU
gettext in the package. In other words, if a
gettextize, he should go the whole way, make the
necessary remaining changes and commit his changes to the CVS.
Otherwise the following damages will likely occur:
gettextspecific portions in `configure.in', `configure.ac' and
Makefile.infiles depend on the
gettextversion, the use of infrastructure files belonging to different
gettextversions can easily lead to build errors.
gettextthan the other developers, the distribution will be less well tested than if all had been using the same
gettextversion. For example, it is possible that a platform specific bug goes undiscovered due to this constellation.
|webmaster||delorie software privacy|
|Copyright © 2003 by The Free Software Foundation||Updated Jun 2003|