Hi Sean - Some Python ports require these variables to be set in
multiple phases. I don't think setting them in multiple phases hurts the
other ports (those that get the flags during configure or build, and
don't use them in any other phase). Things seem to work right now, and
adding these
Is there any reason that the configure.env variables are automatically
copied to the build and destroot phases?
I ask because most python packages do not use the traditional
'./configure; make; make install' method and instead set things like the
prefix and whatnot in the build or destroot phase.
