Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

flake.nix: Expose all top-level packages #481

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

wentasah
Copy link
Contributor

@wentasah wentasah commented Sep 19, 2024

Previously, the legacyPackages output contained only the content of the rosPackages attribute, but things like colcon, superflore or gazebo were not available there.

With this change, we expose all packages defined in pkgs/default.nix as well as the rosPackages attribute. This is the same as when using just default.nix without flakes. This means that one can simply use

nix shell .#colcon

to have colcon command available.

To maintain backward compatibility, we still keep ROS distro package sets at the top level. Therefore, the same ROS package is available at two places. For example, ros-core from humble is available as:

  • .#humble.ros-core (before and after this commit)
  • .#rosPackages.humble.ros-core (after this commit)

Closes #150.

Previously, the legacyPackages output contained only the content of
the rosPackages attribute, but things like colcon, superflore or
gazebo were not available there.

With this change, we expose all packages defined in pkgs/default.nix
as well as the rosPackages attribute. This is the same as when using
just default.nix without flakes. This means that one can simply use

    nix shell .#colcon

to have colcon command available.

To maintain backward compatibility, we still keep ROS distro package
sets at the top level. Therefore, the same ROS package is available at
two places. For example, ros-core from humble is available as:

- .#humble.ros-core (before and after this commit)
- .#rosPackages.humble.ros-core (after this commit)
@kjeremy
Copy link
Contributor

kjeremy commented Sep 19, 2024

I just ran into this when updating some packages the other day.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

legacyPackages lacks colcon and other tools
2 participants