Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is part of my effort to add support for Nix to ROS. It depends on ros-infrastructure/rospkg#171.
The Nix package manager is often used with NixOS, but it runs on any Linux distribution as well as macOS. In order to fit cleanly into the ROS infrastructure, I am pretending that Nix and NixOS have the traditional package manager and distribution relationship. This means that the rosdep OS key for Nix is
nixos
, even though this key may be used on multiple distributions. When packages are built, the build sandbox prevents OS detection from working anyway, so theROS_OS_OVERRIDE
environment variable is used to force the correct value.rosdep
will not be particularly useful to end users, because its imperative package management style does not fit Nix very well. Instead, it will be used to resolve dependencies when generating packages usingsuperflore
.I am working on adding support for Nix to various ROS projects:
I maintain a Superflore generated nixpkgs overlay and have successfully built over 3600 ROS packages on a Hydra build server (not yet publicly accessible)
I also made a small cleanup to the Arch Linux platform.