RoboStack / RoboStack/robostack.github.io

Add *-devel output to conda-forge packages that require them

Open
#65 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Astro
Stars
385
Forks
36
Avg merge
5h 37m
Merged PRs (30d)
18

Description

A common failure point in robostack is that we have conda-forge C++ libraries packages that do not have an output that can be installed to ensure that all the dependencies required to build a downstream C++ project. This is not an issue if a C++ package already include its headers and only use as public dependencies in its headers conda-forge libraries that also ship their headers in the main package, but as soon a dependency uses in its headers a dependency that ships its headers in a separate *-devel package, we need to have a *-devel output also for that package, or it needs to adds the *-devel package to its run dependencies, but some mantainer may be against this as it goes around the point of splitting *-devel packages.

Problematic packages:

  • qt-main : Depends on libgl-devel, but at runtime it only requires libgl
  • vtk : Depends on qt-main, i.e. inheriting the libgl-devel problem
  • pcl: Depends on qt-main, i.e. inheriting the libgl-devel problem
  • libspnav : Depends on xorg-xorgproto, as @Tobias-Fischer is the maintainer and the package is quite simple probably we can avoid the libspnav-devel output and just add xorg-xorgproto as run dependency.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the listed packages—qt-main, vtk, pcl, and libspnav—and trace which headers and runtime dependencies they expose. Determine whether each needs a *-devel output or an added runtime dependency, then verify that downstream C++ builds receive the required headers without unnecessary runtime packages.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
build-system
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.