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

  Server: rpm5.org                         Name:   Jeff Johnson
  Root:   /v/rpm/cvs                       Email:  jbj@rpm5.org
  Module: rpm                              Date:   17-Aug-2008 18:19:38
  Branch: HEAD                             Handle: 2008081716193800

  Modified files:
    rpm                     VENDOR

  Log:
    - jbj: WR: document the vendor patches.

  Summary:
    Revision    Changes     Path
    2.55        +40 -0      rpm/VENDOR
  ____________________________________________________________________________

  patch -p0 <<'@@ .'
  Index: rpm/VENDOR
  ============================================================================
  $ cvs diff -u -r2.54 -r2.55 VENDOR
  --- rpm/VENDOR	14 Aug 2008 17:57:39 -0000	2.54
  +++ rpm/VENDOR	17 Aug 2008 16:19:38 -0000	2.55
  @@ -470,3 +470,43 @@
                        "rpm -bb" operation.
        ________________________________________________________________________
   
  +  o  Name:           WINDRIVER
  +     Vendor:         Wind River <http://windriver.com/>
  +     Representative: Jeff Johnson <jbj@rpm5.org>
  +     Application:    Wind River Linux
  +     Characteristic: cross-packaging build system
  +     ________________________________________________________________________
  +
  +     Change:         rpm-python-archscore.patch
  +     Purpose:        Use %{_host_vendor} and %{_host_os} for platform.
  +     Reason:         Different conventions for retrofitting platform string.
  +     ________________________________________________________________________
  +
  +     Change:         rpm-white-color-upgrade.patch
  +     Purpose:        Color affinity while upgrading on multilib platforms.
  +     Reason:         When performing an upgrade, if we are capable of
  +                     installing multiple colors (elf32/elf64), we need to
  +                     verify that a white (color 0) package should be upgraded. 
  +
  +                     The upgrade rules are:
  +                       If the package is white, and is noarch, it can always
  +                       be upgraded.
  +
  +                       If the package is white, and not noarch, we only
  +                       upgrade if the arch is the same (or in the compatible
  +                       list).
  +         
  +                     Compatible arch's are stored in: _<arch>_compat_arch
  +
  +                     Example of x86_32 and i686:
  +                       _i686_compat_arch i686 x86_32
  +                       _x86_32_compat_arch i686 x86_32
  +                     Order does not mean anything in this list.. one is not
  +                     "more compatible" then another.
  +     ________________________________________________________________________
  +
  +     Change:         wrs-rpm-variants.patch
  +     Purpose:        Permit configurable arch strings.
  +     Reason:         Allow additional architectures to be added via a
  +                     "_known_arch" list. This is useful to allow for new
  +                     variants w/o having to modify RPM each time.
  @@ .