Ruben Arts

Solving package management with pixi @prefix_dev

[prefix.dev @prefix_dev]

We wrote a blog that's a little different from what we normally publish.

It's more focused towards starting out with ROS, and avoiding the complexity of installation. Is this interesting content for you? Should we make more of this?

https://t.co/PcwZ7Q969K

#ROS #ROS2 #robotics

[prefix.dev @prefix_dev]

Isaac ROS 5.0 is out and you can install it with Pixi!

https://t.co/ZNVZ9PsVxe

#NVIDIA #IsaacROS #ROS #AI

[Ruben Arts @rarts_ruby]

It was a play on letters with the word prefix, that was easy to pronounce and remember

[Ruben Arts @rarts_ruby]

Should we build Pixi for Nix packages and call it Nixi?

[trevor manz @trevmanz]

Building bridges between open-source projects is a big part of why I joined @marimo_io.

I got to know the @prefix_dev folks through @SciPyConf, and worked together to make computational research easier to reproduce and share.

Special thanks to Julian and @rarts_ruby!

[prefix.dev @prefix_dev]

The Pixi team is at ROSCON in Toronto - come find the yellow backpacks if you want to chat! We keep spotting Pixi in so many cool robotics projects and it's making us proud. To get a glimpse of what we're working on, join the talk about the EU CRA this afternoon!

[prefix.dev @prefix_dev]

If you see one of these people #ROSCON, they are likely from https://t.co/agh4KWzret! Come say hi, we're friendly! 💛

@OpenRoboticsOrg

[prefix.dev @prefix_dev]

We made it easy to install Isaac ROS! The new `isaac-forge` repository contains many upstream NVIDIA Isaac ROS packages to make them installable with Pixi. You can test it today on your #NIVIDA #Jetson!

No docker needed!

https://t.co/m4HyXF9wRg

[prefix.dev @prefix_dev]

Congratulations to the Mojo 1.0 release @Modular! So glad to have you in our community, and seeing @clattner_llvm on stage with `pixi` in the background was definitely a highlight for us.

[prefix.dev @prefix_dev]

Use pixi global to install any project from source now.

Pixi global supports the full package spec to configure the neccesary information to install it directly, without a pixi.toml.

[prefix.dev @prefix_dev]

Building a git repo that never heard of Pixi used to mean forking it.

Now you declare the build backend inline and Pixi builds it from source.

[prefix.dev @prefix_dev]

Using an NVIDIA Jetson, BTW

#pytorch #nvidia #jetson

[RoboStack @RoboStack]

Don't forget to join the RoboStack Community Meeting today!

Thu 20 Aug; 16:00 CET

https://t.co/hosiEeKH8W

[Ruben Arts @rarts_ruby]

@alvgaona @github Went to X to see if it was just me. Guess it's not ;)

[Alvaro @alvgaona]

Same but with https://t.co/TipRiXwD4f

[prefix.dev @prefix_dev]

PEP 723 only covers Python and PyPI, so Pixi reads tool.pixi for the rest.

Which means conda dependencies in a standalone script.

[prefix.dev @prefix_dev]

As our server grows (600+ channels!) we had to redesign our channel page. It offers you an easier way to find your own or other interesting channels to fetch packages from!

[prefix.dev @prefix_dev]

We've been driving one of the biggest changes to the conda ecosystem since its inception: repodata v3.

Extras, conditional dependencies, and variant flags, expressed directly in the repodata. Now in beta 👇

https://t.co/L0UuazsbHO

[Zed @zeddotdev]

If your disk isn’t critically struggling with available space, are you even #Rusting?

[SciPyConf @SciPyConf]

🛠️ Talk Spotlight: Why does scipy use pixi.toml? @rarts_ruby explains how Pixi solves scientific Python's toughest dependency challenges; C++, Rust, CUDA, Fortran, all in one tool 🚀 #SciPy2026 🔗 https://t.co/C08CDhqkNQ