Feedstock license: BSD-3-Clause
Home: https://github.com/ros-industrial-consortium/tesseract
Package license:
Summary: Tesseract robotics motion planning framework
Name | Downloads | Version | Platforms |
---|---|---|---|
Installing tesseract-robotics-superpack
from the tesseract-robotics
channel can be achieved by adding tesseract-robotics
to your channels with:
conda config --add channels tesseract-robotics
conda config --set channel_priority strict
Once the tesseract-robotics
channel has been enabled, tesseract-robotics-superpack
can be installed with conda
:
conda install tesseract-robotics-superpack
or with mamba
:
mamba install tesseract-robotics-superpack
It is possible to list all of the versions of tesseract-robotics-superpack
available on your platform with conda
:
conda search tesseract-robotics-superpack --channel tesseract-robotics
or with mamba
:
mamba search tesseract-robotics-superpack --channel tesseract-robotics
Alternatively, mamba repoquery
may provide more information:
# Search all versions available on your platform:
mamba repoquery search tesseract-robotics-superpack --channel tesseract-robotics
# List packages depending on `tesseract-robotics-superpack`:
mamba repoquery whoneeds tesseract-robotics-superpack --channel tesseract-robotics
# List dependencies of `tesseract-robotics-superpack`:
mamba repoquery depends tesseract-robotics-superpack --channel tesseract-robotics
If you would like to improve the tesseract-robotics-superpack recipe or build a new
package version, please fork this repository and submit a PR. Upon submission,
your changes will be run on the appropriate platforms to give the reviewer an
opportunity to confirm that the changes result in a successful build. Once
merged, the recipe will be re-built and uploaded automatically to the
tesseract-robotics
channel, whereupon the built conda packages will be available for
everybody to install and use from the tesseract-robotics
channel.
Note that all branches in the tesseract-robotics/tesseract-robotics-superpack-feedstock are
immediately built and any created packages are uploaded, so PRs should be based
on branches in forks and branches in the main repository should only be used to
build distinct package versions.
In order to produce a uniquely identifiable distribution:
- If the version of a package is not being increased, please add or increase
the
build/number
. - If the version of a package is being increased, please remember to return
the
build/number
back to 0.