using a macro in ExclusiveArch

[Dennis Gilmore]

El Thu, 5 Jan 2012 15:20:09 +0100
Michael Schwendt <mschwendt at gmail.com> escribió:
> On Thu, 5 Jan 2012 08:11:07 -0600, DG (Dennis) wrote:
> 
> > > > Is it significant that all three filenames end in "-srpm"? Or 
> > > > should this be considered a bug in Koji?
> > > 
> > > I think the -srpm in there is not important.
> > > 
> > > $ ls /etc/rpm
> > > macros.color   macros.fjava     macros.mono-srpm   macros.systemd
> > > macros.dist    macros.gconf2    macros.ocaml-srpm  macros.texlive
> > > macros.emacs   macros.ghc-srpm  macros.perl
> > > macros.faldor  macros.jpackage  macros.prelink
> > the -srpm is there because the langugaes can provide other language
> > specific macros in a file without -srpm  the -srpm is to define that
> > the macros are needed at srpm creation time and are slightly special
> > because of it. the idea of them is to make it pretty easy to add a
> > arch to a language by modifying one place rather than hundreds.
> > 
> > by having the macros.ghc-srpm  a ghc-common or ghc-filesystem or
> > some such package can provide macros.ghc which has macros for rpm
> > createion and not for srpm creation
> 
> So, it's just a namespace issue, a slightly more unique file name,
> isn't it? To avoid file conflicts.
> 
> RPM loads all files named macros.*

correct. just to avoid file namespace conflicts

Dennis