configure_requires MUST be static, and can NEVER be programmatic.
That's why it exists in the first place.
(This response may not get to the list Eric)
Adam K
Eric Wilhelm wrote:
# from Andreas J. Koenig
# on Monday 17 March 2008 22:34:
(3) mention configure_requires
Does that have meaning in this context?
If configure_requires is a compile-time requirement, and is required to
process the optional_features, then I don't think it can be a
requirement in the optional_features.
If things reach that stage of complexity, I think one of the
dependencies for that feature should be a distribution which has a
configure_requires of its own.
--Eric
