Our great sponsors
| nix-home | ros2nix | |
|---|---|---|
| 1 | 1 | |
| 5 | 17 | |
| - | - | |
| 6.6 | 0.0 | |
| 10 days ago | over 6 years ago | |
| Nix | Nix | |
| - | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
nix-home
-
Nix is the ultimate DevOps toolkit
https://github.com/pwm/nix-home
The readme was/is more of a short note to myself than for users, nevertheless this is how i manage my entire home env on my mac and it works beautifully.
ros2nix
-
Nix is the ultimate DevOps toolkit
Thanks for the response!
> This is difficult to answer without knowing more details.
The situation specifically is the ROS ecosystem, where metadata is managed in these package.xml files:
https://github.com/ros2/rclcpp/blob/master/rclcpp/package.xm...
The federated nature of the ecosystem has led to a culture where it's very normal to be building dozens of these at once, in the same workspace together, often from multiple repos (the repo above has four in it). So there are several build tools which automate the work of examining a source workspace and building all the packages within it in the correct topological order, respecting build_depend tags. The newest of these tools (colcon) has actually made the package.xml optional in many cases, as it can examine CMakelists, setup.py, BUILD, etc, and discover for itself what the dependencies are.
Your "distribution" of ROS is formed by listing all the packages and repos in this big file, for which there is other tooling to manage pulling dependency sources, whatever: https://github.com/ros/rosdistro/blob/master/foxy/distributi...
Anyway, so the existing ROS/nix efforts (1) seem to basically consume all of this package/distribution metadata at once and generate a giant parallel structure of nix definitions (eg https://github.com/lopsided98/nix-ros-overlay/blob/master/di...), which I fear would be completely opaque to users and any system which required everyone to leave behind these existing workflows would be an immediate non-starter.
I think the ideal scenario (and what it would look like if I built this myself based on debs) would be that you could source the "base" workspace as usual (enter the nix-shell?), and check out source, build packages as usual with colcon, the usual workspace-building tool, but there'd be an extra plugin/verb/flag for it, which would make it build each package as a nix package instead of into the usual installspace. The verb would generate the nix definitions on the fly, and probably handle the invocation and build-parallelism side of it as well.
[1]: https://github.com/acowley/ros2nix, https://github.com/lopsided98/nix-ros-overlay
What are some alternatives?
nickel - Better configuration for less
haskell-nix - Nix and Haskell in production
nix-ros-overlay - ROS overlay for the Nix package manager
rosdistro - This repo maintains a lists of repositories for each ROS distribution
nixos - My NixOS Configurations
nix-1p - A (more or less) one page introduction to Nix, the language.
vaultenv - Launch processes with Vault secrets in the environment
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
rclcpp - rclcpp (ROS Client Library for C++)
nixos - NixOS Configuration