Find why your devShell, package, etc depends on something interactively!
`nix-tree --derivation .#devShells.x86_64-linux.default`
Find why your devShell, package, etc depends on something interactively!
`nix-tree --derivation .#devShells.x86_64-linux.default`
Is there a way to see why a Flake DevShell depends on a given package easily?
`nix path-info -r .#devShells.x86_64-linux.default` seems obvious but no worky
Particularly, this one sounds:
> Currently, Flake outputs remain an ad-hoc attribute set with mere suggestions rather than rules around what may be exposed and where.
original toot https://en.osm.town/@jakehamilton@hachyderm.io/114491557286210432
How we use Nix with Flakes ❄❄❄❄
https://qeef.srht.site/post/how-we-use-nix-with-flakes/
It looks like we use Nix with flakes since cradle to the grave.
Considering Nix flakes being experimental, that’s scary.
And Nix laungage itself does not help, neither so many conventions and confusions one needs to keep in mind.
Today at 2pm Pacific, Nix creator and Determinate Co-Founder Eelco Dolstra is presenting on Configurable Flakes at Planet Nix! Come watch in person (room 101) or watch the live stream from anywhere in the world: https://www.youtube.com/watch?v=yhfDtRRTmY8
How it feels to chew Nix gum
@jakehamilton Does Snowfall Lib have any bits that could be used to publish outputs from the flake?
I'm thinking spit the things I'm building in my flake into a listing first but eventually maybe a little website.
Then again it may be outside the scope and there's other projects?...
Say, is there anyone in my network who knows how #NixFlakes work? I'm struggling getting a nix flake with my nodejs development environment for linux and macos to run quickly on mac. It takes about 1.6 seconds to fire up `nix develop` on linux (already too long) but 6.4 seconds on mac.
Man, #nixFlakes make normal things unnecessarily hard:
- git submodules
- #gitAnnex tracked files
- files from a git smudge filter in general
- always this stupid architecture you have to carry around (x86_64-linux et al.)
- more stuff to remember (ah, it's `legacyPackages` now, alright...)
The pinning and lockfile is cool. So is the composability. But it still feels like too many restrictions that are just not there in normal base nix...
I gave ❄️ #nixFlakes another shot for my laptop :nixos: #NixOS config. Indeed, if you keep your repo nice and *dirty*, it will eat :gitannex: files tracked with #gitAnnex - otherwise it wont, a huge blocker for me. So with this I can hop onto the flakes train - which begins to feel like a hard requirement in near future to get things done with NixOS. Everything is just flakes, meh...
Give a man a flake, busy him for a day. Teach a man to nix, frustrate them for a lifetime.
I just finished building a reproducible environment for my #BitRitter app via #NixFlakes. This way, it should be easier to ove things into #NixPkgs when i am ready, since all dependencies and build instructions are already there.
I need to clean up a bit, but i am happy with the first results.
Next to #AlpineLinux or rather #PostmarketOS, #NixOS (Mobile) will be the second target for my use case.
I have no idea what I fucked up, but it seems that somewhere in the last 4 commits I made it so that my computer is now stuck on the #Plymouth splash screen and #GDM is not showing up. Quiting plymouth allows me to reach a tty.
Any #NixOS pros here willing to help a poor soul out, please?
https://github.com/filipdutescu/yggdrasil
#Nix #NixFlake #NixFlakes #Flake #Flakes #Disko #Linux #GNOME
ℹ️ Hello nix lovers, we have automated our mastodon server even further now, with automated daily updates and deployments of nix flake lock file updates.
▶️ Pinned to channel 23.11
▶️ Renovate[bot] updates nix flake deps on a daily basis
▶️ Auto-merge of nix flake lock file updates (if tests are ✅)
▶️ Automated deployment of main branch using a custom github-action
Your feedback is welcome, I'm sure we still have a lot to improve 📈
Ngl, as much as I love #Nix, #NixOs and #NixFlakes, I find debugging flake errors absolutely horrendous… traces only show internals, not my flake, error messages are veeery generic and usually contain a low amount of details as well