Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Track packages that are released in ROS build farm but are/should be in conda-forge

Ouverte
  • Quelque chose ne va pas ?
#17 12 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
À l'abandon
Stack technique
cmake, debian
Domaine
build-system, devops

Piste de recherche

Commencez par le tableau des paquets et les issues liées de conda-forge, rosdistro et autres issues connexes ; comparez les paquets qui sont dupliqués et vérifiez si les paquets vendor ajoutent des fichiers. Le travail est considéré comme terminé lorsque le projet dispose d’une méthode documentée et systématique pour identifier les paquets qui devraient utiliser conda-forge au lieu d’être reconstruits via Bloom.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

The ROS Debian binary packages that are released via Bloom are essentially a distribution of software that builds on top of another distribution of software (the base Debian/Ubuntu repositories). This relation is similar to the one that in the conda world exists between conda-forge and bioconda channels, and in a sense is the same relation that we would like to create between conda-forge and robostack.

Over the time some packages that we not ROS-specific (i.e. they did not depend on the ROS communication middleware) were released with Bloom for several reasons. The major reason is that it was much faster and easier to get a package published via Bloom rather then by going through the actual Debian/Ubuntu packaging process, while in some other cases a package was indeed available in Debian/Ubuntu repos, but the version available in the repos was not recent enough, and it was not possible to update it due to Debian policies for updates in already released distros.

In the case of robostack, given that getting new packages in conda-forge is relatively easy and fast, and the same holds for updating the version of existing packages, I think it make sense to avoid to re-build packages that are or should be in conda-forge even if they are release in bloom/rosdistro, but rather we should have some systematic way to skip them and install the conda-forge version instead. I am not sure what is the proper way of doing so, but for the time being I opened this issue to track the occurrences of this pattern that I spot.

Package repo It is already in conda-forge? rosdistro package name Does the rosdistro package also adds some files? Related issue(s)
https://github.com/pybind/pybind11 https://github.com/conda-forge/pybind11-feedstock pybind11_catkin in ROS1, pybind11_vendor in ROS2 Yes https://github.com/RoboStack/ros-noetic/issues/19
https://github.com/OctoMap/octomap https://github.com/conda-forge/octomap-feedstock octomap No https://github.com/ros/rosdistro/issues/26527
https://github.com/flexible-collision-library/fcl https://github.com/conda-forge/fcl-feedstock fcl No https://github.com/ros/rosdistro/pull/27789
https://github.com/IntelRealSense/librealsense No librealsense No https://github.com/robotology/robotology-superbuild/issues/564
https://github.com/borglab/gtsam Yes gtsam No https://github.com/ros/rosdistro/pull/23198
https://github.com/ethz-adrl/ifopt No ifopt No
https://github.com/stack-of-tasks/pinocchio https://github.com/conda-forge/pinocchio-feedstock pinocchio No
https://github.com/oxfordcontrol/osqp Soon, https://github.com/conda-forge/staged-recipes/pull/13587 osqp_vendor Yes, the CMake config files for the osqp_vendor CMake package, and the osqp_vendor-extras.cmake file. See https://github.com/tier4/osqp_vendor
https://github.com/OGRECave/ogre https://github.com/conda-forge/ogre-feedstock rviz_ogre_vendor Yes, it also installs the CMake config files for the rviz_ogre_vendor CMake files, and some additional related files. Furthermore, just on Windows the used ogre also statically links a locally built copy of freetype and zlib.
https://github.com/stack-of-tasks/eigenpy Yes eigenpy No.
https://tvm.apache.org/ https://github.com/conda-forge/libtvm-feedstock tvm_vendor Yes, it even enables some options while compiling tvm, that are related to vulkan and spirv, that I am not sure if they are available in conda-forge.

Just for ROS2, there are a few more in https://github.com/ros2/?q=vendor .

Langage dominant
Astro
Étoiles
385
Forks
36
Merge moyen
3 h 7 min
PR mergées (30 j)
12

Préparer son environnement

Nous n'avons pas encore vérifié les fichiers d'installation de ce projet. Commencez par son README, et consultez notre guide de la première contribution pour les étapes générales.

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de RoboStack/robostack.github.io

Toutes les issues de RoboStack/robostack.github.io

Issues similaires

Plus d'issues Build System

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.