The better approach (than the tarball with static content) is to write a generator.
The original installplatform generator was way way way too complex to be maintainable because it attempted every possible platform/vendor combination and that was just too much. But now that RPMTAG_ARCH is DEAD! DEAD! DEAD! *and it isn't ever coming back, you'll refigger/rejigger your predefined macro preferences when the time comes ;-). What you have with YAML in libcouinfo is a healthy starting point for better, and will easily adapt to JSON/BSON input in a MongoDB going "forward". hth 73 de Jeff On Apr 7, 2011, at 4:29 PM, Per Øyvind Karlsen wrote: > RPM Package Manager, CVS Repository > http://rpm5.org/cvs/ > ____________________________________________________________________________ > > Server: rpm5.org Name: Per Øyvind Karlsen > Root: /v/rpm/cvs Email: pkarl...@rpm5.org > Module: rpm Date: 07-Apr-2011 22:29:52 > Branch: HEAD Handle: 2011040720295200 > > Modified files: > rpm cpu-os-macros.tar.gz > > Log: > fix %_arch to be canonical for %ix86, x86_64 & sparc > > Summary: > Revision Changes Path > 1.3 BLOB rpm/cpu-os-macros.tar.gz > ____________________________________________________________________________ > > (cd rpm && \ > uudecode <<'@@ .' && \ > mv cpu-os-macros.tar.gz cpu-os-macros.tar.gz.orig && \ > xdelta patch cpu-os-macros.tar.gz.xdelta cpu-os-macros.tar.gz.orig > cpu-os-macros.tar.gz && \ > rm -f cpu-os-macros.tar.gz.orig cpu-os-macros.tar.gz.xdelta) > Index: rpm/cpu-os-macros.tar.gz > ============================================================================ > @@ . > ______________________________________________________________________ > RPM Package Manager http://rpm5.org > CVS Sources Repository rpm-...@rpm5.org ______________________________________________________________________ RPM Package Manager http://rpm5.org Developer Communication List rpm-devel@rpm5.org
