Buy GNU books!
|[ < ]||[ > ]||[ << ]||[ Up ]||[ >> ]||[Top]||[Contents]||[Index]||[ ? ]|
The maintainer of a package has many responsibilities. One of them is ensuring that the package will install easily on many platforms, and that the magic we described earlier (see section 9. The User's View) will work for installers and end users.
Of course, there are many possible ways by which GNU
might be integrated in a distribution, and this chapter does not cover
them in all generality. Instead, it details one possible approach which
is especially adequate for many free software distributions following GNU
standards, or even better, Gnits standards, because GNU
is purposely for helping the internationalization of the whole GNU
project, and as many other good free packages as possible. So, the
maintainer's view presented here presumes that the package already has
a `configure.in' file and uses GNU Autoconf.
gettext may surely be useful for free packages
not following GNU standards and conventions, but the maintainers of such
packages might have to show imagination and initiative in organizing
their distributions so
gettext work for them in all situations.
There are surely many, out there.
gettext methods are now stabilizing, slight adjustments
might be needed between successive
gettext versions, so you
should ideally revise this chapter in subsequent releases, looking
12.1 Flat or Non-Flat Directory Structures 12.2 Prerequisite Works 12.3 Invoking the
12.4 Files You Must Create or Alter 12.5 Autoconf macros for use in `configure.in' 12.6 Integrating with CVS
|webmaster||delorie software privacy|
|Copyright © 2003 by The Free Software Foundation||Updated Jun 2003|