haskell-nix VS nix-ros-overlay

Compare haskell-nix vs nix-ros-overlay and see what are their differences.

haskell-nix

Nix and Haskell in production (by Gabriel439)

nix-ros-overlay

ROS overlay for the Nix package manager (by lopsided98)
Our great sponsors
  • OPS - Build and Run Open Source Unikernels
  • SonarLint - Deliver Cleaner and Safer Code - Right in Your IDE of Choice!
  • Scout APM - Less time debugging, more time building
haskell-nix nix-ros-overlay
3 2
960 63
- -
0.2 8.9
5 months ago 6 days ago
Nix Nix
- Apache License 2.0
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

haskell-nix

Posts with mentions or reviews of haskell-nix. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-06-02.

nix-ros-overlay

Posts with mentions or reviews of nix-ros-overlay. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-04-09.
  • Package override not applying to Nix-shell / Cmake?
    1 project | reddit.com/r/NixOS | 14 Jan 2022
    I believe this might be due to me also using the ROS overlay for Nix (https://github.com/lopsided98/nix-ros-overlay). Some packages that I'm using from ROS also require PCL, so I suspect that Nix might be ignoring my CUDA-enabled overlay and using the regular PCL package in order to meet the required dependencies. I'm not too sure how to confirm this...
  • Nix is the ultimate DevOps toolkit
    21 projects | news.ycombinator.com | 9 Apr 2021
    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?

When comparing haskell-nix and nix-ros-overlay you can also consider the following projects:

rfcs - The Nix community RFCs

nixpkgs - Nix Packages collection

Cabal - Official upstream development repository for Cabal and cabal-install

haskell.nix - Alternative Haskell Infrastructure for Nixpkgs

rosdistro - This repo maintains a lists of repositories for each ROS distribution

static-haskell-nix - easily build most Haskell programs into fully static Linux executables

nixos-config - Personal collection of NixOS config files

nix-1p - A (more or less) one page introduction to Nix, the language.

nickel - Better configuration for less

vaultenv - Launch processes with Vault secrets in the environment

pndev - CLI tool for es-development