Knobi wrote:P.S. Is there a possibility to commit that component to the PAPI-C CVS when finished?
Apologies for the long delay in responding. We're entering new territory here. We want to encourage people to develop novel, useful and innovative components for PAPI. We also want to provide a mechanism to distribute those components as broadly as possible. However, we're concerned about accepting the burden for testing and maintaining components produced by others as part of the mainline PAPI source tree.
We may be able to set up a separate repository for third party components and we may somehow require components to pass some kind of acceptance testing before being incorporated into the source tree. But this is all new ground to explore.
Maybe this is an opportunity to use something like sourceforge as a clearing house for PAPI Components.
For any of this to work smoothly, we need to develop a mechanism whereby components can be separately compiled and discovered at run-time rather than the clunky inclusion in the build at configure time the way we do things now.
I welcome other ideas on this topic. Any thoughts?