Not everything is #bsd or even #nix

Not everything is #bsd or even #nix

> goes down the rabbit hole of the origin of "legacyPackages" naming

> finds no good reason (yada yada nested package attributes and nix flake show whatever) that would ever allow it to be properly addressed in #nixpkgs, the one package set most people will always have to interact with

> decides to refer to upstream #nix as legacyNix because it makes just as much sense

> goes down the rabbit hole of the origin of "legacyPackages" naming

> finds no good reason (yada yada nested package attributes and nix flake show whatever) that would ever allow it to be properly addressed in #nixpkgs, the one package set most people will always have to interact with

> decides to refer to upstream #nix as legacyNix because it makes just as much sense

cross-posted from: discourse.nixos.org/t/how-nixos-is-built/67468

cross-posted from: discourse.nixos.org/t/how-nixos-is-built/67468

Hey, there's a #Guix#London #meetup planned for Tuesday next week:

https://www.meetup.com/guix-social/events/308234219/

Time: Tuesday 8th July at 6pm
Location: 20 Farringdon St, EC4A 4AB

Being troubled by some unmatched parenthesis? Come speak to us!

In love with #Nix / #NixOS and curious to know more about Guix? Join us!

(Please register on meetup.com or DM me as your name needs to be passed to the building reception so they can let you in.)

Hey, there's a #Guix#London #meetup planned for Tuesday next week:

https://www.meetup.com/guix-social/events/308234219/

Time: Tuesday 8th July at 6pm
Location: 20 Farringdon St, EC4A 4AB

Being troubled by some unmatched parenthesis? Come speak to us!

In love with #Nix / #NixOS and curious to know more about Guix? Join us!

(Please register on meetup.com or DM me as your name needs to be passed to the building reception so they can let you in.)

Decided to spend the afternoon working from the pub. I've been fighting a really annoying "builds in the devshell, fails in the derivation" bug all day, so a pint seemed necessary.

Was working away, minding my own business, when a bar fly in the corner starts loudly professing to the other bar flies that they reckon they're the only normal ones in the place.

I can't decide if they were right or not...

🤔 😂 🤔

#Nix

Decided to spend the afternoon working from the pub. I've been fighting a really annoying "builds in the devshell, fails in the derivation" bug all day, so a pint seemed necessary.

Was working away, minding my own business, when a bar fly in the corner starts loudly professing to the other bar flies that they reckon they're the only normal ones in the place.

I can't decide if they were right or not...

🤔 😂 🤔

#Nix

Using #Nix as a package manager on top of a #Guix system is really easy, just a matter of adding '(service nix-service-type)' to the system services and reconfiguring.

This gives us access to Nix-land, e.g.:

nix-channel --add https://nixos.org/channels/nixpkgs-unstable
nix-channel --update
nix-shell --packages cowsay --run "cowsay hello"

A couple more steps if you want to save things in a profile, see:

https://guix.gnu.org/manual/en/html_node/Miscellaneous-Services.html#Nix-service

Handy! E.g. for certain things that are still difficult to package under Guix.

❄️ Why We’re Moving on From #Nix • Railway

｢ The biggest problem with Nix is its commit-based package versioning. Only the latest major version of each package is available, with versions tied to specific commits in the nixpkgs repo ｣

https://blog.railway.com/p/introducing-railpack

｢ Flakes have not meaningfully improved in several years, “crucial” fixes and features for Flakes have stalled in open pull requests headed almost entirely by Determinate Systems, and the feature itself has been both declared unstable as well as stable by the Nix development team and Determinate Systems respectively. This absurdity is entirely self-inflicted and can be resolved by any party at any time, but participants choose otherwise ｣

https://kilo.bytesize.xyz/flakes-have-failed

#flakes #nix #nixos