As suggested by David FETTER in: http://marc.theaimsgroup.com/?l=openpkg-users&m=111420775907164&w=2
...the file '.rpmmacros' will be searched in all the usual places, but additionally in ~/.openpkg. That means that should the OpenPKG user do nothing new, he can expect no changed behaviour. Should he place a '.rpmmacros' file in the ~/.openpkg directory however, he can expect all variable and macros declarations therein to be effective. Except for command line declarations, the ~/.openpkg/.rpmmacros file is now the definitive location for RPM variables and macros. This new feature can be used to discriminate OpenPKG's RPM bahaviour from other RPM installations on the system. Should the OpenPKG user want to build packages in a different location than the system (Red Hat, SuSE...) RPM installation specifies, he can rest assured that the system RPM commands will use ~/.rpmmacros while OpenPKG will use ~/.openpkg/.rpmmacros. This feature exists in the OpenPKG bootstrap RPM and bourne shell packages since today: $ wget ftp://ftp.openpkg.org/current/SRC/openpkg-20050518-20050518.src.rpm $ wget ftp://ftp.openpkg.org/current/SRC/openpkg-20050518-20050518.src.sh $ /prefix/bin/openpkg rpm --rebuild \ ftp://ftp.openpkg.org/current/SRC/openpkg-20050518-20050518.src.rpm Please don't make the mistake of building with an older OpenPKG and expecting it to pick its RPM variables and macros from the new location. Regards, Michael -- Michael Schloh von Bennewitz <[EMAIL PROTECTED]> Development Team, Operations Northern Europe Cable & Wireless Telecommunications Services Tel +49-89-92699-227, Fax +49-89-92699-808
pgpAwXyMmZOx9.pgp
Description: PGP signature
