libibmad provides low layer IB functions for use by the IB diagnostic
and management programs.
In CentOS 6 and 7 it was not part yet of the rdma-core package. It is
however usually part of a OFED installation and thus should also be
added on conda-forge.
The license was imported from libibmad-1.3.13-1.el7.x86_64.rpm at
/usr/share/doc/libibmad-1.3.13/COPYING.
Checklist:
[x] if you have added a CDT, it appears in the cdt_slugs.yaml file and
you have rerun the script python gen_cdt_recipes.py.
[ ] ~~if you have changed the CDT generator code (rpm.py), you have bumped
the build number in conda_build_config.yaml and have remade all of the
recipes via running python gen_cdt_recipes.py --force~~
[ ] ~~if you have added a custom CDT recipe, you have added the name of the CDT
with custom: true in the cdt_slugs.yaml file.~~
[x] all CDT recipes have build number set by {{ cdt_build_number }} for
old-style/legacy CDTs or {{ cdt_build_number|int + 1000 }} for new-style CDTs
[x] if you see a warning about a CDT not having a license, you have added the
license_file key in the cdt_slugs.yaml file with the path to the appropriate
license in licenses/
libibmad provides low layer IB functions for use by the IB diagnostic and management programs. In CentOS 6 and 7 it was not part yet of the rdma-core package. It is however usually part of a OFED installation and thus should also be added on conda-forge. The license was imported from libibmad-1.3.13-1.el7.x86_64.rpm at /usr/share/doc/libibmad-1.3.13/COPYING.
Checklist:
cdt_slugs.yaml
file and you have rerun the scriptpython gen_cdt_recipes.py
.rpm.py
), you have bumped the build number inconda_build_config.yaml
and have remade all of the recipes via runningpython gen_cdt_recipes.py --force
~~custom: true
in thecdt_slugs.yaml
file.~~{{ cdt_build_number }}
for old-style/legacy CDTs or{{ cdt_build_number|int + 1000 }}
for new-style CDTslicense_file
key in thecdt_slugs.yaml
file with the path to the appropriate license inlicenses/