In reply to @schuelermine:matrix.org
Has the Determinate Systems blog post from an hour ago been discussed here already?

In reply to @johnrizzo1:matrix.org
Just read it. What are your thoughts?

Hey. I'm thinking about what would be the best way (best practices) to maintain a set of custom nixpkgs.lib style functions for local use. I guess there's a few considerations:

• Flake or something else. Or rather, a different repository from the code using it or not. I assume I might use it in multiple repositories eventually, but maybe initially it would be easiest to not juggle multiple repositories that develop and use it.

• How to get it to code using it. Should I put it in an overlay as a package? Do we have something like a reserved for private use namespace, guaranteed to not be used for anything except by local use? :) Would be annoying if I come up with a random string for local use and then someone publishes a package with the same name!

Actually, what's the attrset that lib.nixosSystem passes to the modules? I think in that I have inputs for my flake inputs (specialArgs = { inputs = ...; }). Does that attrset also get passed to the nixpkg-style packages? No, I think that's pkgs, since I've seen functions that take an attrset with package names?

In reply to @sliedes:hacklab.fi

Hey. I'm thinking about what would be the best way (best practices) to maintain a set of custom nixpkgs.lib style functions for local use. I guess there's a few considerations:

• Flake or something else. Or rather, a different repository from the code using it or not. I assume I might use it in multiple repositories eventually, but maybe initially it would be easiest to not juggle multiple repositories that develop and use it.

• How to get it to code using it. Should I put it in an overlay as a package? Do we have something like a reserved for private use namespace, guaranteed to not be used for anything except by local use? :) Would be annoying if I come up with a random string for local use and then someone publishes a package with the same name!

Actually, what's the attrset that lib.nixosSystem passes to the modules? I think in that I have inputs for my flake inputs (specialArgs = { inputs = ...; }). Does that attrset also get passed to the nixpkg-style packages? No, I think that's pkgs, since I've seen functions that take an attrset with package names?

In reply to @sr.estegosaurio:matrix.org
I'm trying to make my system use nouveau to benchmark stuff but I think now it's only running off the iGPU.

In reply to @sr.estegosaurio:matrix.org
I've disabled all nvidia related stuff on my config and thus I don't have the propietary drivers loaded.

In reply to @sliedes:hacklab.fi

Hey. I'm thinking about what would be the best way (best practices) to maintain a set of custom nixpkgs.lib style functions for local use. I guess there's a few considerations:

• Flake or something else. Or rather, a different repository from the code using it or not. I assume I might use it in multiple repositories eventually, but maybe initially it would be easiest to not juggle multiple repositories that develop and use it.

• How to get it to code using it. Should I put it in an overlay as a package? Do we have something like a reserved for private use namespace, guaranteed to not be used for anything except by local use? :) Would be annoying if I come up with a random string for local use and then someone publishes a package with the same name!

Actually, what's the attrset that lib.nixosSystem passes to the modules? I think in that I have inputs for my flake inputs (specialArgs = { inputs = ...; }). Does that attrset also get passed to the nixpkg-style packages? No, I think that's pkgs, since I've seen functions that take an attrset with package names?

In reply to @sr.estegosaurio:matrix.org
And according to modprobe nouveau is loaded in the kernel.

If youre on xorg then xrandr --listproviders is good

In reply to @emilazy:matrix.org
for naming, perhaps consider something reverse DNS-based

In reply to @sr.estegosaurio:matrix.org
And according to modprobe nouveau is loaded in the kernel.

In reply to @schuelermine:matrix.org
Has the Determinate Systems blog post from an hour ago been discussed here already?

In reply to @magic_rb:matrix.redalder.org

If youre on xorg then xrandr --listproviders is good

In reply to @sliedes:hacklab.fi
Yeah, I thought about that. There's also the tension of wanting it to be short and wanting it to be unique :D

In reply to @sr.estegosaurio:matrix.org
Not on Xorg :/

In reply to @johnrizzo1:matrix.org
From a technical point of view, what problem do you think they are solving that isn't being solved by nixos. I see a lot of things like AWS IaM integration, semtantic versioning, etc.

I should’ve phrased myself better. I think it could be benign. Obviously all of the functionality they offer could be offered by the Nix open source community with some work, and them positioning themselves as Nix, but more user-friendly, is troubling since it creates a hostile relationship as Nix itself also wants to become user-friendly.

In reply to @johnrizzo1:matrix.org
From a technical point of view, what problem do you think they are solving that isn't being solved by nixos. I see a lot of things like AWS IaM integration, semtantic versioning, etc.

I should’ve phrased myself better. I think it could be benign. Obviously all of the functionality they offer could be offered by the Nix open source community with some work, and them positioning themselves as Nix, but more user-friendly, is troubling since it creates a hostile relationship as Nix itself also wants to become more user-friendly.

In reply to @kfears:matrix.org
Just FYI: the top-1 committer to CppNix in the recent months is Eelco Dolstra, and he's also Co-Founder of DetSys, and a very long-time maintainer of CppNix (he's also the creator of Nix the concept)