Feedstock license: BSD-3-Clause

Home: https://github.com/icub-tech-iit/ergocub-software

Package license: BSD-3-Clause

Summary: Software and configuration files required to simulate and run the ergoCub humanoid robot.

This feedstock builds the following packages:

• ergocub-models: Depedency-free package that contains the URDF models of the different version of the ergoCub robot.
• libergocub-software: Plugins and executables used for ergoCub simulations and for operating the ergoCub robot, it depends on ergocub-models.
• ergocub-software : Meta-package that install all the software provided by the feedstock, i.e. libergocub-software and ergocub-models.

Current build status

GitHub Actions
Azure	Variant Status osx_64

Current release info

Name	Downloads	Version	Platforms

Installing ergocub-software

Installing ergocub-software from the conda-forge channel can be achieved by adding conda-forge to your channels with:

conda config --add channels conda-forge
conda config --set channel_priority strict

How to use

conda install ergocub-models ergocub-software libergocub-software

mamba install ergocub-models ergocub-software libergocub-software

# for adding to your local project
pixi add ergocub-models ergocub-software libergocub-software
# for installing globally
pixi global install ergocub-models ergocub-software libergocub-software

Search package versions

It is possible to list all of the versions of ergocub-models available on your platform:

conda search ergocub-models --channel conda-forge

mamba search ergocub-models --channel conda-forge

pixi search ergocub-models --channel conda-forge

# Search all versions available on your platform:
mamba repoquery search ergocub-models --channel conda-forge

# List packages depending on `ergocub-models`:
mamba repoquery whoneeds ergocub-models --channel conda-forge

# List dependencies of `ergocub-models`:
mamba repoquery depends ergocub-models --channel conda-forge

About conda-forge

conda-forge is a community-led conda channel of installable packages. In order to provide high-quality builds, the process has been automated into the conda-forge GitHub organization. The conda-forge organization contains one repository for each of the installable packages. Such a repository is known as a feedstock.

A feedstock is made up of a conda recipe (the instructions on what and how to build the package) and the necessary configurations for automatic building using freely available continuous integration services. Thanks to the awesome service provided by Azure, GitHub, CircleCI, AppVeyor, Drone, and TravisCI it is possible to build and upload installable packages to the conda-forge anaconda.org channel for Linux, Windows and OSX respectively.

To manage the continuous integration and simplify feedstock maintenance, conda-smithy has been developed. Using the conda-forge.yml within this repository, it is possible to re-render all of this feedstock's supporting files (e.g. the CI configuration files) with conda smithy rerender.

For more information, please check the conda-forge documentation.

Terminology

feedstock - the conda recipe (raw material), supporting scripts and CI configuration.

conda-smithy - the tool which helps orchestrate the feedstock. Its primary use is in the construction of the CI .yml files and simplify the management of many feedstocks.

conda-forge - the place where the feedstock and smithy live and work to produce the finished article (built conda distributions)

Updating ergocub-software-feedstock

If you would like to improve the ergocub-software 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 conda-forge channel, whereupon the built conda packages will be available for everybody to install and use from the conda-forge channel. Note that all branches in the conda-forge/ergocub-software-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.

Feedstock Maintainers

• @Nicogene
• @traversaro