rosdistro
nix-1p
rosdistro | nix-1p | |
---|---|---|
6 | 7 | |
882 | 860 | |
0.7% | - | |
10.0 | 4.7 | |
about 17 hours ago | 16 days ago | |
Python | Nix | |
GNU General Public License v3.0 or later | - |
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.
rosdistro
-
How to install python script dependencies automatically on ROS1 Noetic?
I have added their rosdep names (found here) to my packages.xml (see the end of this post), but even after running catkin-make and trying to run the module, the script throws a ModuleNotFound exception at the UTM package meaning that the package was never installed.
-
Stopping ros buildfarm emails
I second this. Just remove the package by removing whatever you added to the rosdistro repo when submitting/publishing the package.
-
What to do about GPU packages on PyPI?
The business about mapping from PyPI to system dependencies is an important one, and (having not read the entire thread) I do hope that gets some attention— it's particularly curious that it's been this long and it hasn't, given Python's often-role as a glue language.
Another example of an ecosystem maintaining mappings out to system packages is ROS and rosdep:
https://github.com/ros/rosdistro/blob/master/rosdep/base.yam...
Now it's interesting because ROS is primarily concerned with supplying a sane build-from-source story, so much of what's in the rosdep "database" is the xxxx-dev packages, but in the case of wheels, it would be more about binary dependencies, and those are auto-discoverable with ldd, shlibdeps, and the like. In Debian (and I assume other distros), the binary so packages are literally the library soname + abi versions, so if you have ldd output, you have the list of exactly what to install.
-
If I use ros2 built from source, can I use "sudo apt install ros-distro-package" to install packages??
The names you use for the tag (and the other dependency tags in your package.xml) are used by rosdep to figure out what needs to be installed. The name doesn't necessarily correspond to the apt or pip package name, but most of the time it's the same. For example, for matplotlib: https://github.com/ros/rosdistro/blob/24141d9063fddd6eeca7f1db9e721fa8d600c62f/rosdep/python.yaml#L6296
-
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
-
HUGE ROS Noetic Update -- 93 New and 119 Update Packages
Thanks for the feedback. I bumped a couple of the core devs and got the change reverted and it is now merged. It should be in the next Noetic release.
nix-1p
- Nix – A One Pager
- Nix Lang in One Page
-
pellets: manage your packages with a configuration file
Fair enough. I've also had a couple of programs which weren't packaged already, fortunately it's quite easy to do so most of the time (or to just fall back to a distrobox container or flatpak in the worst case). If you decide to try it out, nix-1p and Nix Pills were great resources for me to get familiar with Nix and NixOS in a short time-span.
-
Why the Windows Registry sucks technically (2010)
Wouldn't say there's a steep learning curve for the language itself, it's pretty easy to get a grasp around it imo. Here's a helpful page I used to quickly get familiar with the language: https://github.com/tazjin/nix-1p
What's rather messy about Nix is nixpkgs with its helper functions all over the place alongside pretty shallow / non-existent documentation (which is unrelated to the language). Thankfully they've started to work on that recently: https://discourse.nixos.org/t/documentation-team-flattening-...
-
Nix is the ultimate DevOps toolkit
I wrote a language tutorial for only the language a while back, and have gotten the feedback that it has helped a lot of people - maybe it'd clear something up for you: https://github.com/tazjin/nix-1p
-
Getting help is hard
For Nix language things I really like this page: https://github.com/tazjin/nix-1p
What are some alternatives?
nix-ros-overlay - ROS overlay for the Nix package manager
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
haskell-nix - Nix and Haskell in production
rfcs - The Nix community RFCs
dh-virtualenv - Python virtualenvs in Debian packages
nix-home - Nix + HM = <3
aptly - aptly - Debian repository management tool
nixos - My NixOS Configurations
nix - Nix, the purely functional package manager
nickel - Better configuration for less