It's be nice to split MPI Install phase into multiple phases

[gpaulsen]

It'd be nice to split the MPI Install phase into multiple phases.
For example, it'd be nice to have an MPI configure phase, which would allow for capturing detailed (and summary) configure output.
And then an MPI build phase (if desired, often this is less interesting)
And then is Install phase at all interesting? Probably not.

In this particular use-case I'm trying to gather some more information about how the MPI product was configured across different organizations runs across time, looking for specific features either configured in or out. (for example which components).

[mallove]

It'd be nice to split the MPI Install phase into multiple phases.
For example, it'd be nice to have an MPI configure phase, which would allow for capturing detailed (and summary) configure output.
And then an MPI build phase (if desired, often this is less interesting)
And then is Install phase at all interesting? Probably not.

In this particular use-case I'm trying to gather some more information about how the MPI product was configured across different organizations runs across time, looking for specific features either configured in or out. (for example which components).

Hi Geoff -- I believe this can currently be accomplished through configuration, e.g., the Autotools plugin has a configure_options parameter, which can be queried via the MTT reporter. So, e.g., this report turns up MPI installations configured with-ofi=/opt/amazon (in the configure_options string).