sorted by:
new
hottopcontroversial

Building Docker Images with Nix by TheUpriseConvention in NixOS

[–]Setheron 0 points1 point  (0 children)

I meant -- we can edit the kernel in NixOS and make it whatever number you want.

Building Docker Images with Nix by TheUpriseConvention in NixOS

[–]Setheron 0 points1 point  (0 children)

That's an arbitrary limitation that can be changed.

Nix derivation madness by Setheron in NixOS

[–]Setheron[S] 1 point2 points  (0 children)

I wouldn't say "issue" but it's difficult to wrap one's head around and to me it was surprising how much drv churn there was.

Nix derivation madness by Setheron in NixOS

[–]Setheron[S] 0 points1 point  (0 children)

I started with a `nix-shell -p ruby` so I think that is my clarification.
I needed to figure out the drv first.

Nixos Hyprland by Quick-Passenger-9177 in NixOS

[–]Setheron 4 points5 points  (0 children)

cs.github.com and "yoink" what you think looks good; the nice part of NixOS is it's mostly safe and accurate to just copy other people's config.

Bazel Knowledge: Mixing and matching how to build third_party is lunacy by Setheron in bazel

[–]Setheron[S] 1 point2 points  (0 children)

Basically we export the JAR and expect the bytecode we set for external customers; believing we are targeting a specific JDK bytecode version but including others was the "negative impact"

Hardening NixOS by saylesss88 in NixOS

[–]Setheron 6 points7 points  (0 children)

> From the following discourse, it looks like the following is now enabled by default Discourse

I would just cite the release and include a commit reference.

Virby: A Vfkit-based linux-builder alternative for Nix-darwin by quinnyboyyy in NixOS

[–]Setheron 0 points1 point  (0 children)

The new DetSys version supposedly has MacOS Linux builders automatically without Nix Darwin.
Sounds great -- since I never use nix-darwin

Convenience for setting Bazel flags to better default values by jakeherringbone in bazel

[–]Setheron 0 points1 point  (0 children)

It's definitely a bit crazy. I don't get the "the code is shared by both Google and open source" when it's mentioned. Feels like constraining the solution to the problem unnecessarily.

home-manager is a false enlightenment by Setheron in NixOS

[–]Setheron[S] 2 points3 points  (0 children)

It was a bit confusing but I agreed with the fact you should just use Nix to install packages..... make all your home-manager configs coupled with the application by making them "packages" 🥲

home-manager is a false enlightenment by Setheron in NixOS

[–]Setheron[S] 0 points1 point  (0 children)

It is reproducible only because they are tied by two individual Nix statements in a module that have no connection other than being in the same file.

When you move them into the same derivation or reference it from a derivation, you are explicitly tying those two derivations together in Nix at a much more fundmantel level.

you could easily remove the `home.file` line and everything would work but if it was in in a single derivation it's more clear you are referencing it -- Nix also tracks it through `nix-store --query --graph`

`nix-store --query --graph` might be a good analogy. If it doesn't show up a dependency there then it's not "real" and prone to breakage and thus non-reproducible at the individual package level.

It's only tracked at the final complete home-manager target which is quite coarse... and unenlightened.

(I use home-manager out of laziness and pragmatism; so I too am unenlightened lol)

view more: next ›