PATH_GPGV in -current

[Alex Kiernan]

Russ Allbery <rra at stanford.edu> writes:

> Alex Kiernan <alexk at demon.net> writes:
> 
> > Is there a reason why PATH_GPGV is that rather than _PATH_GPGV
> > (leading underscore), given how thats all the other paths into
> > configure work? Or was it just a typo?
> 
> > Just got confused over it!
> 
> Yeah, all of the other ones should be changed to drop the underscore.  :)
> 

<grin> It was one of those where you keep running configure & keep
staring at and can't for the life of you work out why its not working!

> The comment in paths.h explains some of it.

Ah hadn't seen that bit of rationale.

> All those _PATH_* constants violate the reserved namespace in the C
> standard, so they all need to change to INN_PATH_* at some point,
> and the variables in the Makefiles and therefore in configure.in
> should probably match, possibly modulo the INN_ part so that our
> configure macros can be reused by other people.  So when I put in
> gpgv, I used the naming scheme that I want to move us to in the long
> run (that cleanup is currently slated for 2.5).
> 

Makes sense - thanks.

-- 
Alex Kiernan, Principal Engineer, Development, Thus PLC