Heads-up: %define vs %global in specs

[Ville Skyttä]

On Tuesday 05 January 2010, Tom "spot" Callaway wrote:
> On 01/05/2010 11:50 AM, Daniel P. Berrange wrote:
> > What exactly do you mean 'no longer work' ? Can we expect to get a formal
> > RPM build error for this bogus construct, or will it silently build and
> > do the wrong thing ? From your long description, it sounds like the
> > latter, which means maintainers should audit their spec files to identify
> > these bogus macros
> 
> The easy way to be sure you're not hitting this is to not use %define.
> Sed will fix your packages up quickly. ;)

Smiley noted, but blindly doing that has potential to break stuff too.  Here's
one example that works as intended with %define but not with %global:

http://cvs.fedoraproject.org/viewvc/devel/bash-completion/bash-completion.spec?r1=1.46&r2=1.47