Post

Remember that experiment of using @flox.dev to replace Homebrew? Now it's official. flox.dev/docs/tutoria...

> You need a broader set of software. Homebrew has a sizeable collection of packages, but the Flox Catalog is based on Nixpkgs, the largest collection of packages in the world. I publish a couple of binaries to homebrew, do I now need to also publish them with nix or to nixpkgs?

11/12/24, 10:19 pm0 reposts4 likes

Michael Stahnke

@stahnma.us

11 Dec 2024

There is a very decent chance they are already in nixpkgs. If they're not, you can join the Flox community slack (link in our github.com/flox/flox readme) and we can help you get them there.

github.comGitHub - flox/flox: Developer environments you can take with youDeveloper environments you can take with you. Contribute to flox/flox development by creating an account on GitHub.

verdverm

@verdverm.com

11 Dec 2024

to be honest, as a project maintainer, the proliferation of package managers has been annoying. We have actually gone the opposite direction to simplify and have decided to only support binary downloads from github and our homebrew tap.

tomberek.bsky.social

@tomberek.bsky.social

12 Dec 2024

What ecosystem? I presume something supporting static builds?

I believe the @flox.dev team is working on something like this.

Michael Stahnke

@stahnma.us

11 Dec 2024

We are! It's not all done yet, but if you're interested and want to try some things out, hit us up in our community slack. (using bitly because the whole URI is super long and ugly) bit.ly/3D8jbDX

bit.lySlack