I have no objections to this. Unfortunately, I don't have the time to work on it, but we'd be glad to look at pull requests to introduce this functionality. :-)
> On Mar 23, 2017, at 6:07 PM, Kevin Buckley > <kevin.buckley.ecs.vuw.ac...@gmail.com> wrote: > > Another than occured to me whilst looking around this > was whether the OpenMPI SRPM might benefit from > being given proper "Software Collections" package > capability, as opposed to having the "install in opt" > option. > > I don't claim to have enough insight to say either way > here, however the Software Collections documentation > > https://www.softwarecollections.org/en/docs/guide/#sect-Converting_a_Conventional_Spec_File > > suggests that it's possible to use a traditional sepcfile > for both system and SCL builds, and I could see that > were "OpenMPI" to be used as the SCLo "provider" > tag then things would end up living under > > /opt/OpenMPI/openmpi-202/ > > which isn't that far away from what you have, with the > "install in opt" now. > > > Very much just a Request for Comments than a suggestion though, > Kevin > _______________________________________________ > devel mailing list > devel@lists.open-mpi.org > https://rfd.newmexicoconsortium.org/mailman/listinfo/devel -- Jeff Squyres jsquy...@cisco.com _______________________________________________ devel mailing list devel@lists.open-mpi.org https://rfd.newmexicoconsortium.org/mailman/listinfo/devel
