ROS stuff: part 1

[Pandapip1]

See #11713

See #112404

Things done

• Built on platform(s)
  • x86_64-linux
  • aarch64-linux
  • x86_64-darwin
  • aarch64-darwin
• For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
  • sandbox = relaxed
  • sandbox = true
• Tested, as applicable:
  • NixOS test(s) (look inside nixos/tests)
  • and/or package tests
  • or, for functions and "core" functionality, tests in lib/tests or pkgs/test
  • made sure NixOS tests are linked to the relevant packages
• Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
• Tested basic functionality of all binary files (usually in ./result/bin/)
• 24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)
  • (Package updates) Added a release notes entry if the change is major or breaking
  • (Module updates) Added a release notes entry if the change is significant
  • (Module addition) Added a release notes entry if adding a new NixOS module
• Fits CONTRIBUTING.md.

---

Add a 👍 reaction to pull requests you find important.

[kjeremy]

Are you planning on adding rosdep keys for these upstream and coordinating with @lopsided98's https://github.com/lopsided98/nix-ros-overlay?

[Pandapip1]

[Are you planning on] coordinating with @lopsided98's https://github.com/lopsided98/nix-ros-overlay?

Yes. This PR is based on that overlay.

Are you planning on adding rosdep keys for these upstream

I'm not familiar with ROS; I'm basing this off of that overlay and will have my roommate (who does use ROS) test this once it's done. If you've got any similar suggestions, they are very welcome!

I've taken a look at rosdep and it does seem reasonable to add keys for nixpkgs. The only potential issue I foresee is that you can't 'install' libraries with nix; I'll see if I can find a way around this.

[lopsided98]

I would suggest not bothering with any dependencies of Gazebo classic or ROS Noetic, since they both go EOL in January.

[Pandapip1]

I would suggest not bothering with any dependencies of Gazebo classic or ROS Noetic, since they both go EOL in January.

I'm not sure what version of ROS my roommate needs, so I'll continue packaging everything in the overlay for the time being.

UPDATE: My roommate is using kinetic and jazzy, so we're good. I'm not sure which versions of the gazebo build tools correspond to which versions of gazebo yet though, so I'll err on the side of adding too much, and then shrinking as needed.

[nim65s]

Thanks for working on this, @Pandapip1 !

[nim65s]

There is a misssing hash, but othewise this seems to work well on both x86_64-linux and aarch64-darwin

[nim65s]

@Pandapip1 : any news about this ?

[Pandapip1]

This stuff all works last I checked, but nobody's reviewed it.

[nim65s]

Ok, thanks. Could you fix the conflicts ?

[Pandapip1]

Rebased.

[nim65s]

Also, the latest LTS (Jetty) is available, ref. https://github.com/gazebo-tooling/gazebodistro/blob/master/collection-jetty.yaml for its versions

[nim65s]

Maybe something with gazebosim/gz-common#590 can be tried ?

[Pandapip1]

Too many failing CI checks for me to consider that yet