Linux

48697 readers

1389 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
No misinformation
No NSFW content
No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago

MODERATORS

[email protected]

Flakes aren't real and cannot hurt you: a guide to using Nix flakes the non-flake way (jade.fyi)

submitted 11 months ago by [email protected] to c/[email protected]

25 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 11 months ago (1 children)

Wut. It’s just as reproducible, flakes are mostly just a common unifying API with some extra CLI sugar for usability.

[–] [email protected] 6 points 11 months ago (1 children)

While that is true, it's also r13y on another level: Reproducible evaluation. That mostly stems from pure eval and locking.

In the "before times", you'd get your Nix expressions from some mutable location in the Nix path, so running i.e. a nixos-rebuild on your configuration could produce two different eval results when ran at two different times, depending on whether anything about your channel configuration changed in the mean time. This cannot happen with flakes as all inputs are explicitly given and locked.

You could achieve the same using niv etc. before but that had its own issues.

[–] [email protected] 2 points 11 months ago (1 children)

It was usually recommended to lock to inputs anyhow with all the fetchers requiring a hash which I hated having to manually update & like the UX flakes provides (I really wish they supported more than Git & Mercurial tho). You can still have different evals tho if you point to latest.tar.zstd or other non-hashed thing like a branch where the referred to can change & it won’t reproduce. I haven’t used channels in years, but doesn’t that just refer to the running system, not using Nix to build projects?

[–] [email protected] 1 points 11 months ago (1 children)

I haven’t used channels in years, but doesn’t that just refer to the running system, not using Nix to build projects?

I have no idea what you're trying to say here.

[–] [email protected] 1 points 11 months ago (1 children)

Aren‘t channels for NixOS, and you’d use overlays for building packages? Now you can do that all with flakes.

[–] [email protected] 2 points 11 months ago

No, channels are a simply a mechanism for managing what's in your NIX_PATH.