This document summarizes the efforts of current and future xSDK member packages to achieve compatibility with the xSDK community policies. Below only short descriptions of each policy are provided. The full description is available here and should be considered when filling out this form.
*** A good example of how to complete this form can be found in the PETSc version.
Please, provide information on your compability status for each mandatory policy, and if possible also for recommended policies. If you are not compatible, state what is lacking and what are your plans on how to achieve compliance.
For current xSDK member packages: If you were not fully compatible at some point, please describe the steps you undertook to fulfill the policy. This information will be helpful for future xSDK member packages.
Website: <package website>
| Policy | Support | Notes |
|---|---|---|
| M1. Support xSDK community GNU Autoconf or CMake options. | Full | Short-expanation-here; optional link for more extensive details if needed, see below. M1 details |
| M2. Provide a comprehensive test suite for correctness of installation verification. | Full | Short-expanation-here; optional link for more extensive details if needed, see below. M2 details |
| M3. Employ user-provided MPI communicator (no MPI_COMM_WORLD). Don't assume a full MPI 3 implementation without checking. Provide an option to prevent any changes to MPI error-handling if it is changed by default. | Full | None. |
| M4. Give best effort at portability to key architectures (standard Linux distributions, GNU, Clang, vendor compilers, and target machines at ALCF, NERSC, OLCF). | Full | None. |
| M5. Provide a documented, reliable way to contact the development team. | Full | None. |
| M6. Respect system resources and settings made by other previously called packages (e.g. signal handling). | Full | None. |
| M7. Come with an open source (BSD style) license. | Full | Use 2-clause BSD license. |
| M8. Provide a runtime API to return the current version number of the software. | Full | None. |
| M9. Use a limited and well-defined symbol, macro, library, and include file name space. | Full | None. |
| M10. Provide an xSDK team accessible repository (not necessarily publicly available). | Full | None. |
| M11. Have no hardwired print or IO statements that cannot be turned off. | Full | None. |
| M12. For external dependencies, allow installing, building, and linking against an outside copy of external software. | Full | None. |
| M13. Install headers and libraries under <prefix>/include and <prefix>/lib. | Full | None. |
| M14. Be buildable using 64 bit pointers. 32 bit is optional. | Full | Packages supports both 32 and 64 bit under same API. |
| M15. All xSDK compatibility changes should be sustainable. | Full | None. |
| M16. The package must support production-quality installation compatible with the xSDK install tool and xSDK metapackage. | Full | None. |
M1 details : optional: provide more details about approach to addressing topic M1.
M2 details : optional: provide more details about approach to addressing topic M2.
| Policy | Support | Notes |
|---|---|---|
| R1. Have a public repository. | Partial | Repo is access controlled but available as release tarfile. |
| R2. Possible to run test suite under valgrind in order to test for memory corruption issues. | Full | None. |
| R3. Adopt and document consistent system for error conditions/exceptions. | None | None. |
| R4. Free all system resources acquired as soon as they are no longer needed. | Full | None. |
| R5. Provide a mechanism to export ordered list of library dependencies. | None | None. |
| R6. Document versions of packages that it works with or depends upon, preferably in machine-readable form. | None | None. |
| R7. Have README, SUPPORT, LICENSE, and CHANGELOG files in top directory. | None | None. |