Description
For #101 , we want to publish legate-boost conda packages to the legate channel (https://anaconda.org/legate/repo).
This captures the work to do that.
Benefits of this work
- simplifies installation of
legate-boost
Acceptance Criteria
- conda packages are built and tested in CI here
- conda package name should be
legate-boost (with the -)
- pushing a tag to the repo triggers publishing to the
legate conda channel
Approach
Patterns that might be borrowed from RAPIDS libraries, including:
pyproject.toml instead of setup.py
scikit-build-core as a build backend instead of scikit-build
rapids-cmake to manage dependencies
rapids-dependency-file-generator to keep different lists of dependencies consistent
For an example of this, see how cuvs conda packages are built:
Notes
legate-core source, for reference: https://github.com/nv-legate/legate.core
Description
For #101 , we want to publish
legate-boostconda packages to thelegatechannel (https://anaconda.org/legate/repo).This captures the work to do that.
Benefits of this work
legate-boostAcceptance Criteria
legate-boost(with the-)legateconda channelApproach
Patterns that might be borrowed from RAPIDS libraries, including:
pyproject.tomlinstead ofsetup.pyscikit-build-coreas a build backend instead ofscikit-buildrapids-cmaketo manage dependenciesrapids-dependency-file-generatorto keep different lists of dependencies consistentFor an example of this, see how
cuvsconda packages are built:Notes
legate-coresource, for reference: https://github.com/nv-legate/legate.core