How to handle nixpkgs as a [very large] git repo

[abathur]

@TheBlackBeans

Are there any particular workarounds to handle such a massive repo? How do you work with it in your day to day life?

I don’t think there’s a ton to be done about some of the operations being slow, but I chafed at this a bit myself.

I tried gitstatusd but still wasn’t super pleased so I ended up writing a bash prompt plugin to claw back that time in most contexts:

• gh: GitHub - abathur/lilgit: a smol (quick) git status prompt plugin
• post here: Slow prompt in large git repos? speed up with lilgit

I’ve been picking at converting more of my own packages to flakes over the past few months and have one almost ready for lilgit. Not looking at my notes, but I think the main thing I wanted to fix is figuring out why the rust component stopped building against nixpkgs-unstable on darwin back in October.