Le Jeudi 23 Janvier 2003 11:13, Buchan Milne a �crit : > Olivier Thauvin wrote:
Rpm is fully base on macros, all setting are macros. If you define a macros on command line, you will overwrite the default, an spec defined macros, you can specify an alternative personnal rpmmacros too, here some example: _topdir: my default is ~/RPM/ with all structure (BUILD, SPEC, RPMS, SRPMS...) _tmpdir: $RPM_BUILD_ROOT is within vendor = vendor tag distribution = ditrib tag packager... --target only define _target_cpu... If you want build same rpm for plf and mdk in same time, you can't because it will use same dir, else you define another build dir, you can overwrite SPEC an SOURCE dir too. rpm --help for more, I don't remember all, rpm --showrc help a lot too. > You would notice the rpmmacros file I posted would define all the right > macros based on the release number. If the release number contains mdk, > ut uses vendor MandrakeSoft etc. Credit to Ben for the initial example. > I also use it to seperate the RPMs I build, so Mandrake RPMs live in > ~/rpm/mdk, plf RPMs live in ~/rpm/plf etc. > > I did this because when using Guillaume's method, you can't build mdk > and plf RPMs simultaneously, which is a problem if you want to build a > quick PLF rpm while you have an OpenOffice or multiple samba builds for > stable releases going ... also, too often I forgot to switch > environments ... > > Buchan -- Linux pour Mac !? Enfin le moyen de transformer une pomme en v�ritable ordinateur. - JL. Olivier Thauvin - http://nanardon.homelinux.org/
