Graham✈️✈️

I think unfortunately this is a problem with autotools. If a dep requires a library but doesn't use pkg-config, often the only way of adding it is often using `CFLAGS`...

Yeah I was thinking a CAVEAT, but we can put it in the DESCRIPTION section. I think one thing that we need to be careful of is qualifying the issue....

Basically we want to be able to say ```perl $ENV{CFLAGS} = '-O3' unless defined $ENV{CFLAGS}; ``` except just around the execution of the build.

> If I read the plugin code correctly, it already appends to existing env vars. The issue with the gdal and proj builds is that they are set somewhere in...

> I'm not sure that should be done in this plugin though as there may be other places that we want to modify these variables. The autoconf plugin might be...

> Any such settings are probably best done in the relevant alienfile given the potential variability of default flags. Or I am misunderstanding this point. No, that is exactly the...

> I've experimented with Alien::proj, and passing CFLAGS and CXXFLAGS args to the configure call does override any env vars. That reminds me we should document CXXFLAGS I think only...

Possibly, at least on an opt-in basis. We avoid re-running the alienfile at "runtime" because it brings in a lot of extra dependencies into your runtime process. This would primarily...

Yes in either share or system install `_alien/alienfile` can be used to reinstall the alienized package without going through a cpan client or re-installing the Alien dist. This could be...

It can also be a useful reference to the exact recipe that was used to do the install.