Can someone explain to me the advantage of using #nixflakes for #nixos or homemanger config? I understood that it was just a way of pinning requirements.

j'ai juste mit le repo du framework en input de mon #NixFlakes
https://gitlab.com/pinage404/nix-sandboxes/-/blob/155f4f7f37a4d3fc6ff9375277e3d91526a41311/c/flake.nix#L21

exporté via une variable d'environnement le chemin du framework dans le Nix store
https://gitlab.com/pinage404/nix-sandboxes/-/blob/155f4f7f37a4d3fc6ff9375277e3d91526a41311/c/flake.nix#L42

puis utilisé cette variable, comme n'importe quel chemin
https://gitlab.com/pinage404/nix-sandboxes/-/blob/155f4f7f37a4d3fc6ff9375277e3d91526a41311/c/maskfile.md#L14

I guess i am too stupid (read: unexperienced) to get #anyrun running in my #NixOS #NixFlakes. The #HomeManager description in the readme confuses me where to put it in my config.
https://github.com/Kirottu/anyrun

#nixos users, what's your favorite thing about it?

I installed it on my second laptop yesterday, then went running back to #endeavouros for now. My curiosity has been piqued though.

Observations:
- declarative system (users, packages was as far as I got)
- homegrown, but hard to learn configuration language
- #NixGui is the only configuration GUI, but didn't launch (crashed) for me, even after enabling #nixflakes

Two very interesting flows:
- desktop setup as code
- reproducible environment

Wow, I am beyond words. The feeling you get when installing a fresh version of a distro to test on using an external drive, just to have it somehow wipe your GRUB and corrupt the #NixOS partition that you hadn't yet backed up newest configs...it's almost indescribable 😭😭😭🖕

Now I have to work on my project AND rebuild the beautiful Nix setup I had from somewhat recent config backups...thank God #nixflakes makes it that much easier! 🤗😑 :nixos: :arch:

Spent the day wrapping my head around #nixos.
Managed to get it running with #i3wm in virtualbox, but still failing with #leftWM.
Yet to figure out #nixFlakes, as it seems to be THE thing now and move to real hardware.
What's running on your local NixOS?

Found the solution, it was in the wiki and helpfully named exactly like one might expect: https://nixos.wiki/wiki/flakes#NixOS

That said, the next step is to get it pulling in the #OctoPrint flake, which apparently can do URLs but that isn't working for me ("error getting status, not a directory") so we've pulled down a local copy and have successfully used the nix flake metadata command from there.

Next, doing some edits so that the magic numbers aren't clashing.

Just gonna mention that it's taken seven hours from the start of this #LibreOps dive into #NixOS and #NixFlakes and most of that has just been to get the basic functionality working. For someone without decades of tech background, this would be tantamount to impossible. I think about this a lot when working.

Today is about learning. Specifically, #NixOS and #NixFlakes on #aarch64, so that I can print this gorram camera shoe: https://www.thingiverse.com/thing:1721215

This is a form of productively avoiding several things that need doing.

In this case, I'm avoiding the task of rewriting an HTML link assembler shell script in the static site generator, in part because it's terrifying to put my shyte up for anyone to see and comment on and potentially criticize, attack, or take without crediting the appropriate dependencies. Also in part because tech automation going wrong is a huge fear of mine, and being known as the person who inadvertently caused the singularity to start assembling terminators is becoming increasingly a concern as self-modifying codebases and neural networks roam the intertubes. But I digress.

So, today I'm gonna use my procrastination as leverage to accomplish other things which have been procrastinated on. When I do this consistently, eventually I end up with just the one thing in my queue, and having run out of excuses to accomplish it, and with a pile of smaller successes boosting my confidence, the big thing gets done.

Why does this specific task (printing a camera mount shoe) require a deep dive into the ass end of the declarative computing stack? Mainly, because once again I am tired of building, rebuilding, and re-re-building the same solution endlessly. I'm ready to do something that lasts longer and gets crufty more slowly. Half a decade of use, or longer, is the goal here.

It's been nearly a decade since I first installed the #OctoPrint software, and every year or two I've needed to completely re-configure it from scratch. Part of that has been my own lack of cohesive backup solutions for my configs, and part of that is operating system cruft. I made a committment to myself that I'd take the time to do it right with the #EnderV3Pro that I was gifted last holidays, and despite hacking on things for a bit last winter to get a few prints, my committment to that hasn't stuck. So, today I'm poking the Nix Flake for OctoPrint by #viperML (ref: https://github.com/viperML/octoprint-nix/) and using this blogpost by #Tweag (ref: https://www.tweag.io/blog/2020-05-25-flakes/) as a jumping off point. I say "jumping off point" because the blogpost is from two years ago and may not reflect what happens when I actually install this software on my single board computer intended for the print lab.

This is a messy process.

#ThisIsHacking

It's trial and error and sometimes waiting long periods of time for someone to build something that is close enough to my competency stack that I can take an angle grinder to the pointy bits and make it fit into what I'm trying to accomplish.

I use #nixflakes via this shell function in my bashrc b/c flakes aren't on by default:
```
function nixx(){
cmd="nix --experimental-features 'nix-command flakes' "
cmd+="$@"
set -x
nix-shell -p nixFlakes --run "${cmd?}"
set +x
}
```

I use #nixflakes via this shell function in my bashrc b/c flakes aren't on by default:
```
function nixx(){
cmd="nix --experimental-features 'nix-command flakes' "
cmd+="$@"
set -x
nix-shell -p nixFlakes --run "${cmd?}"
set +x
}
```

This way flake commands work in bash:
```
$ nixx flake update
```

I use #nixflakes using this shell function in my bashrc b/c flakes aren't on by default:
```
function nixx(){
cmd="nix --experimental-features 'nix-command flakes' "
cmd+="$@"
set -x
nix-shell -p nixFlakes --run "${cmd?}"
set +x
}
```
This lets you type flake commands at a bash prompt:
```
$ nixx flake update
```

Another weekend wasted fighting with #nixflakes + #haskell. Things that worked months ago are now inexplicably broken. I just can't justify this level of pain. It needs to be as simple, speedy and sensible as `stack new ...` to get started. #nix

@nbathum server outage on the exact evening when I was migrating from #archlinux to NixOS in 2013. :D

Seriously though, not much. Reading Eelco's papers and multi output expressions design documents and literally any #NixFlakes blog post should be a nice way to get solid foundations over a weekend.

As noobs interact more and more with the language, #NixPills is a decent series to build up the language understanding.

#Introduction
I’m a #father, a #filmmaker, dabbler in #engineering of many types.
Technologically, my interests lie in the bleeding edge of possibility wherever I see it.
#nixos #nixflakes #foss
#haskell #GHC #dependentlytyped #dependenttypes #functionalprogramming
#plutus #cardano #smartcontracts #formalmethods #formalverification
#idris #swift #arduino #riscv #Rust
#decentralization #parallelization #biomimicry #buddhism #leftist
#cinelighting #cinematography
#anarchosyndicalism #science

Все это время думал, почему у меня nix все еще v21.05

Вроде бы nix channel у меня 21.11, но все равно пакеты старые.

А сейчас дошло. Я ж юзаю nix flakes и nixpkgs у меня указан во flake.nix. По этому вместо `nixos-rebuild switch --upgrade`, мне нужно обновить flakes.lock (nix flake update), потому что flakes вообще не используют nix channels и там все по своему

#nixos #nixflakes #nixpkgs

In this screenshot: #docker #windows #ubuntu #nix #nixflakes #direnv #homemanager #vscode #postgresql all to make sure that #java development is... ...possible.

Great write up on switching to #nix #flakes #nixflakes #NixOS https://justin.restivo.me/posts/2021-01-09-flakes.html

Every package manager expands until it supports multiple concurrent versions of the same package. Those that cannot expand to support this usecase are replaces by ones that can.

#nixflakes #shitpost