RPM Package Manager, CVS Repository
  http://rpm5.org/cvs/
  ____________________________________________________________________________

  Server: rpm5.org                         Name:   Anders F. Björklund
  Root:   /v/rpm/cvs                       Email:  afb@rpm5.org
  Module: rpm                              Date:   30-Nov-2007 16:55:11
  Branch: HEAD                             Handle: 2007113015551100

  Modified files:
    rpm                     INSTALL

  Log:
    add librpmconstant

  Summary:
    Revision    Changes     Path
    2.61        +9  -7      rpm/INSTALL
  ____________________________________________________________________________

  patch -p0 <<'@@ .'
  Index: rpm/INSTALL
  ============================================================================
  $ cvs diff -u -r2.60 -r2.61 INSTALL
  --- rpm/INSTALL	30 Nov 2007 15:41:18 -0000	2.60
  +++ rpm/INSTALL	30 Nov 2007 15:55:11 -0000	2.61
  @@ -192,10 +192,11 @@
     RPM Executables:       rpm
     (stage 0)              rpmbuild
   
  -  RPM Libraries:         librpmbuild
  -  (stage 1)              librpm 
  +  RPM Libraries:         librpm
  +  (stage 1)              librpmbuild
  +                         librpmconstant
                            librpmdb
  -                         librpmio 
  +                         librpmio
                            librpmmisc
   
     Third-Party Libraries: libpopt     (mandatory)
  @@ -226,10 +227,11 @@
   
   The most important aspects to notice are: librpmbuild requires mainly
   librpm, librpm in turn requires both librpmdb and librpmio, and all
  -librpm* require librpmmisc. Additionally, librpmmisc is a container for
  -the internal local copies of third-party libraries. Finally, notice that
  -the set of third-party libraries at stage 2 can be dynamically choosen
  -at build-time and are not a fixed set.
  +librpm* require librpmmisc. Additionally; librpmmisc is a container for
  +the internal local copies of third-party libraries, and librpmconstant
  +provides RPM API constants (usually to language bindings). Finally,
  +notice that the set of third-party libraries at stage 2 can be dynamically 
  +chosen at build-time and are not a fixed set.
   
   Unfortunately, there are many link-time approaches to handle these
   internal and external dependencies. The currently implemented approach
  @@ .