Should parrot_config report separate inst_ and build variables?

[Andy Dougherty]

Some config variables have two variants, e.g. ldflags_libparrot and 
inst_ldflags_libparrot, intended for use either in the build directory or 
install directory.  Hence a language needs to decide which variant to use, 
depending on whether or not it's building against an installed parrot.

Is that the desired behavior?  Or, perhaps, should the installed version 
of parrot_config *know* that it's the installed version and simply report 
the inst_ version of variables?

On a related note, it might be nice to try to regularize the variable 
names somewhat.  I tend to think the name used by the installed version 
ought to be the simpler, more obvious one; the build directory can use a 
longer, clunkier name.

-- 
    Andy Dougherty		doughera at lafayette.edu