#nixdarwin — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #nixdarwin, aggregated by home.social.
-
You know, I love the idea but I think #NixDarwin is way more trouble than it’s worth. Despite stable, reproducible builds being its raison d'être, I feel like I’m constantly fixing things.
Broken nix dependencies and non-standard Homebrew setup causing issues seem to be the most frequent offenders.
Not to mention how few things are on nix packages and how many are way out of date, I end up using Homebrew for most things anyway, though, admittedly, declaratively.
It’s likely a skill issue, but as much as I like a declarative configuration, I’m not sure I want to invest so much time into knowing all of the underlying systems at the depth needed to get everything set up *exactly* the right way. Add to that the amount of things that can’t be setup in macOS via command line and must be setup interactively, it’s hardly a perfectly reproducible configuration in the first place.
Of course, I’m enough of a masochist that I’ll probably keep trying out of sheer stubbornness anyway. 🫠
Any better alternatives?
-
You know, I love the idea but I think #NixDarwin is way more trouble than it’s worth. Despite stable, reproducible builds being its raison d'être, I feel like I’m constantly fixing things.
Broken nix dependencies and non-standard Homebrew setup causing issues seem to be the most frequent offenders.
Not to mention how few things are on nix packages and how many are way out of date, I end up using Homebrew for most things anyway, though, admittedly, declaratively.
It’s likely a skill issue, but as much as I like a declarative configuration, I’m not sure I want to invest so much time into knowing all of the underlying systems at the depth needed to get everything set up *exactly* the right way. Add to that the amount of things that can’t be setup in macOS via command line and must be setup interactively, it’s hardly a perfectly reproducible configuration in the first place.
Of course, I’m enough of a masochist that I’ll probably keep trying out of sheer stubbornness anyway. 🫠
Any better alternatives?
-
You know, I love the idea but I think #NixDarwin is way more trouble than it’s worth. Despite stable, reproducible builds being its raison d'être, I feel like I’m constantly fixing things.
Broken nix dependencies and non-standard Homebrew setup causing issues seem to be the most frequent offenders.
Not to mention how few things are on nix packages and how many are way out of date, I end up using Homebrew for most things anyway, though, admittedly, declaratively.
It’s likely a skill issue, but as much as I like a declarative configuration, I’m not sure I want to invest so much time into knowing all of the underlying systems at the depth needed to get everything set up *exactly* the right way. Add to that the amount of things that can’t be setup in macOS via command line and must be setup interactively, it’s hardly a perfectly reproducible configuration in the first place.
Of course, I’m enough of a masochist that I’ll probably keep trying out of sheer stubbornness anyway. 🫠
Any better alternatives?
-
You know, I love the idea but I think #NixDarwin is way more trouble than it’s worth. Despite stable, reproducible builds being its raison d'être, I feel like I’m constantly fixing things.
Broken nix dependencies and non-standard Homebrew setup causing issues seem to be the most frequent offenders.
Not to mention how few things are on nix packages and how many are way out of date, I end up using Homebrew for most things anyway, though, admittedly, declaratively.
It’s likely a skill issue, but as much as I like a declarative configuration, I’m not sure I want to invest so much time into knowing all of the underlying systems at the depth needed to get everything set up *exactly* the right way. Add to that the amount of things that can’t be setup in macOS via command line and must be setup interactively, it’s hardly a perfectly reproducible configuration in the first place.
Of course, I’m enough of a masochist that I’ll probably keep trying out of sheer stubbornness anyway. 🫠
Any better alternatives?
-
You know, I love the idea but I think #NixDarwin is way more trouble than it’s worth. Despite stable, reproducible builds being its raison d'être, I feel like I’m constantly fixing things.
Broken nix dependencies and non-standard Homebrew setup causing issues seem to be the most frequent offenders.
Not to mention how few things are on nix packages and how many are way out of date, I end up using Homebrew for most things anyway, though, admittedly, declaratively.
It’s likely a skill issue, but as much as I like a declarative configuration, I’m not sure I want to invest so much time into knowing all of the underlying systems at the depth needed to get everything set up *exactly* the right way. Add to that the amount of things that can’t be setup in macOS via command line and must be setup interactively, it’s hardly a perfectly reproducible configuration in the first place.
Of course, I’m enough of a masochist that I’ll probably keep trying out of sheer stubbornness anyway. 🫠
Any better alternatives?
-
Got a new MacBook from my employer this week (48GB? In this economy!?) and nix-darwin made it quite easy to set it up like the previous machine, including a declarative list of homebrew casks and App Store apps to install. Between that and my Emacs and hammerspoon configs, I quickly felt at home again. #nix #nixdarwin
-
Got a new MacBook from my employer this week (48GB? In this economy!?) and nix-darwin made it quite easy to set it up like the previous machine, including a declarative list of homebrew casks and App Store apps to install. Between that and my Emacs and hammerspoon configs, I quickly felt at home again. #nix #nixdarwin
-
Got a new MacBook from my employer this week (48GB? In this economy!?) and nix-darwin made it quite easy to set it up like the previous machine, including a declarative list of homebrew casks and App Store apps to install. Between that and my Emacs and hammerspoon configs, I quickly felt at home again. #nix #nixdarwin
-
Got a new MacBook from my employer this week (48GB? In this economy!?) and nix-darwin made it quite easy to set it up like the previous machine, including a declarative list of homebrew casks and App Store apps to install. Between that and my Emacs and hammerspoon configs, I quickly felt at home again. #nix #nixdarwin
-
Got a new MacBook from my employer this week (48GB? In this economy!?) and nix-darwin made it quite easy to set it up like the previous machine, including a declarative list of homebrew casks and App Store apps to install. Between that and my Emacs and hammerspoon configs, I quickly felt at home again. #nix #nixdarwin
-
Before I restart my Xcode project from scratch…
Does anyone have experience trying to get an old Xcode project that was running on a ~2016 intel mac with old Xcode, using a C based package dependency, running on a new modern mac that uses nix-darwin? I can’t get it to build.
I am getting weird build errors seemingly related to non existent header file errors. I *suspect* the issue is related to paths somewhere between nix, command line build tools vs xcode, clang stuff from the package, expected paths vs nix paths, etc. However, it may also just be differences in APIs from the old system to the new.
I’ve tried a bunch of things like change the version of clang, interop settings, made sure xcode-select was pointing to xcode not cli tools and whatnot. But I’m stuck. Before I restart this project fresh, if anyone has any potential things to check or tips etc I’m all ears. I’ve tried search and Gemini but to no avail. Any humans out there with suggestions?
-
Before I restart my Xcode project from scratch…
Does anyone have experience trying to get an old Xcode project that was running on a ~2016 intel mac with old Xcode, using a C based package dependency, running on a new modern mac that uses nix-darwin? I can’t get it to build.
I am getting weird build errors seemingly related to non existent header file errors. I *suspect* the issue is related to paths somewhere between nix, command line build tools vs xcode, clang stuff from the package, expected paths vs nix paths, etc. However, it may also just be differences in APIs from the old system to the new.
I’ve tried a bunch of things like change the version of clang, interop settings, made sure xcode-select was pointing to xcode not cli tools and whatnot. But I’m stuck. Before I restart this project fresh, if anyone has any potential things to check or tips etc I’m all ears. I’ve tried search and Gemini but to no avail. Any humans out there with suggestions?
-
Before I restart my Xcode project from scratch…
Does anyone have experience trying to get an old Xcode project that was running on a ~2016 intel mac with old Xcode, using a C based package dependency, running on a new modern mac that uses nix-darwin? I can’t get it to build.
I am getting weird build errors seemingly related to non existent header file errors. I *suspect* the issue is related to paths somewhere between nix, command line build tools vs xcode, clang stuff from the package, expected paths vs nix paths, etc. However, it may also just be differences in APIs from the old system to the new.
I’ve tried a bunch of things like change the version of clang, interop settings, made sure xcode-select was pointing to xcode not cli tools and whatnot. But I’m stuck. Before I restart this project fresh, if anyone has any potential things to check or tips etc I’m all ears. I’ve tried search and Gemini but to no avail. Any humans out there with suggestions?
-
Before I restart my Xcode project from scratch…
Does anyone have experience trying to get an old Xcode project that was running on a ~2016 intel mac with old Xcode, using a C based package dependency, running on a new modern mac that uses nix-darwin? I can’t get it to build.
I am getting weird build errors seemingly related to non existent header file errors. I *suspect* the issue is related to paths somewhere between nix, command line build tools vs xcode, clang stuff from the package, expected paths vs nix paths, etc. However, it may also just be differences in APIs from the old system to the new.
I’ve tried a bunch of things like change the version of clang, interop settings, made sure xcode-select was pointing to xcode not cli tools and whatnot. But I’m stuck. Before I restart this project fresh, if anyone has any potential things to check or tips etc I’m all ears. I’ve tried search and Gemini but to no avail. Any humans out there with suggestions?
-
Before I restart my Xcode project from scratch…
Does anyone have experience trying to get an old Xcode project that was running on a ~2016 intel mac with old Xcode, using a C based package dependency, running on a new modern mac that uses nix-darwin? I can’t get it to build.
I am getting weird build errors seemingly related to non existent header file errors. I *suspect* the issue is related to paths somewhere between nix, command line build tools vs xcode, clang stuff from the package, expected paths vs nix paths, etc. However, it may also just be differences in APIs from the old system to the new.
I’ve tried a bunch of things like change the version of clang, interop settings, made sure xcode-select was pointing to xcode not cli tools and whatnot. But I’m stuck. Before I restart this project fresh, if anyone has any potential things to check or tips etc I’m all ears. I’ve tried search and Gemini but to no avail. Any humans out there with suggestions?
-
In case you heard about #nixos, #nixdarwin, and the Dendritic pattern my new blog post might interest you: https://istvnurbn.me/2026/04/from-dotfiles-to-dendrites/
-
In case you heard about #nixos, #nixdarwin, and the Dendritic pattern my new blog post might interest you: https://istvnurbn.me/2026/04/from-dotfiles-to-dendrites/
-
In case you heard about #nixos, #nixdarwin, and the Dendritic pattern my new blog post might interest you: https://istvnurbn.me/2026/04/from-dotfiles-to-dendrites/
-
In case you heard about #nixos, #nixdarwin, and the Dendritic pattern my new blog post might interest you: https://istvnurbn.me/2026/04/from-dotfiles-to-dendrites/
-
In case you heard about #nixos, #nixdarwin, and the Dendritic pattern my new blog post might interest you: https://istvnurbn.me/2026/04/from-dotfiles-to-dendrites/
-
First day done setting up my nix-darwin config for new MacBook Pro. I almost didn’t do it, but remembered my fondness of NixOS along with a vague memory of being able to use Nix packages on Mac. Well, nix-darwin brings more than just package management. I’m very happy with how the config is going, and so glad I remembered before I got too far down the road of mouse pecking button clicking my way around setting up my new machine. First new machine in 9yrs. Nix for the win. Nix-Darwin has made my decision to go with macOS, over Linux, easier and better.
-
First day done setting up my nix-darwin config for new MacBook Pro. I almost didn’t do it, but remembered my fondness of NixOS along with a vague memory of being able to use Nix packages on Mac. Well, nix-darwin brings more than just package management. I’m very happy with how the config is going, and so glad I remembered before I got too far down the road of mouse pecking button clicking my way around setting up my new machine. First new machine in 9yrs. Nix for the win. Nix-Darwin has made my decision to go with macOS, over Linux, easier and better.
-
Wrote up how I manage dotfiles across macOS and Linux with Nix. One repo, one flake.lock — same shell, editor, and tools on every machine. Home Manager and nix-darwin do the heavy lifting.
-
Wrote up how I manage dotfiles across macOS and Linux with Nix. One repo, one flake.lock — same shell, editor, and tools on every machine. Home Manager and nix-darwin do the heavy lifting.
-
Wrote up how I manage dotfiles across macOS and Linux with Nix. One repo, one flake.lock — same shell, editor, and tools on every machine. Home Manager and nix-darwin do the heavy lifting.
-
Wrote up how I manage dotfiles across macOS and Linux with Nix. One repo, one flake.lock — same shell, editor, and tools on every machine. Home Manager and nix-darwin do the heavy lifting.
-
Wrote up how I manage dotfiles across macOS and Linux with Nix. One repo, one flake.lock — same shell, editor, and tools on every machine. Home Manager and nix-darwin do the heavy lifting.
-
Воспроизводимое изолированное окружение с Nix и DevContainers
Как фулстек разработчику, мне доводилось работать с проектами на совершенно разных технологиях. Как правило, нужно было поправить небольшой баг или сделать небольшую фичу. Для задач такого разряда стек технологий обычно не имеет значения: отладка примерно одинаковая что на JavaScript, что на Haskell, Go или Python. Написать немного кода мне, в общем-то, никогда не было сложно на любом языке, с которым я работал. Но вот что всегда было настоящей проблемой — это запустить и протестировать проект. На это запросто уходили дни: найти нужные версии компиляторов/интерпретаторов, дебаггера, пакетного менеджера и всякого сопутствующего тулинга. Я устал от этого, и придумал, как больше никогда в жизни не устанавливать тулинг вручную.
https://habr.com/ru/articles/1010282/
#nix #devcontainers #docker #reproducibility #nixos #nixdarwin
-
Воспроизводимое изолированное окружение с Nix и DevContainers
Как фулстек разработчику, мне доводилось работать с проектами на совершенно разных технологиях. Как правило, нужно было поправить небольшой баг или сделать небольшую фичу. Для задач такого разряда стек технологий обычно не имеет значения: отладка примерно одинаковая что на JavaScript, что на Haskell, Go или Python. Написать немного кода мне, в общем-то, никогда не было сложно на любом языке, с которым я работал. Но вот что всегда было настоящей проблемой — это запустить и протестировать проект. На это запросто уходили дни: найти нужные версии компиляторов/интерпретаторов, дебаггера, пакетного менеджера и всякого сопутствующего тулинга. Я устал от этого, и придумал, как больше никогда в жизни не устанавливать тулинг вручную.
https://habr.com/ru/articles/1010282/
#nix #devcontainers #docker #reproducibility #nixos #nixdarwin
-
Воспроизводимое изолированное окружение с Nix и DevContainers
Как фулстек разработчику, мне доводилось работать с проектами на совершенно разных технологиях. Как правило, нужно было поправить небольшой баг или сделать небольшую фичу. Для задач такого разряда стек технологий обычно не имеет значения: отладка примерно одинаковая что на JavaScript, что на Haskell, Go или Python. Написать немного кода мне, в общем-то, никогда не было сложно на любом языке, с которым я работал. Но вот что всегда было настоящей проблемой — это запустить и протестировать проект. На это запросто уходили дни: найти нужные версии компиляторов/интерпретаторов, дебаггера, пакетного менеджера и всякого сопутствующего тулинга. Я устал от этого, и придумал, как больше никогда в жизни не устанавливать тулинг вручную.
https://habr.com/ru/articles/1010282/
#nix #devcontainers #docker #reproducibility #nixos #nixdarwin
-
Might be of interest to #Nix users out there:
https://gist.github.com/totoroot/b9684294d599504218e0c655ca56767d
I created a script that helps me audit packages installed vianix profileas I often do that before adding them to my system configuration ❄️
I then tend to forget to remove them after I installed them via my system configuration (as systemPackages or via #HomeManager).
With this script I can later on audit all packages installed, check which binaries they provide and automatically remove them if they were found in my PATH somewhere else.
#NixOS #NixDarwin -
Might be of interest to #Nix users out there:
https://gist.github.com/totoroot/b9684294d599504218e0c655ca56767d
I created a script that helps me audit packages installed vianix profileas I often do that before adding them to my system configuration ❄️
I then tend to forget to remove them after I installed them via my system configuration (as systemPackages or via #HomeManager).
With this script I can later on audit all packages installed, check which binaries they provide and automatically remove them if they were found in my PATH somewhere else.
#NixOS #NixDarwin -
Might be of interest to #Nix users out there:
https://gist.github.com/totoroot/b9684294d599504218e0c655ca56767d
I created a script that helps me audit packages installed vianix profileas I often do that before adding them to my system configuration ❄️
I then tend to forget to remove them after I installed them via my system configuration (as systemPackages or via #HomeManager).
With this script I can later on audit all packages installed, check which binaries they provide and automatically remove them if they were found in my PATH somewhere else.
#NixOS #NixDarwin -
Might be of interest to #Nix users out there:
https://gist.github.com/totoroot/b9684294d599504218e0c655ca56767d
I created a script that helps me audit packages installed vianix profileas I often do that before adding them to my system configuration ❄️
I then tend to forget to remove them after I installed them via my system configuration (as systemPackages or via #HomeManager).
With this script I can later on audit all packages installed, check which binaries they provide and automatically remove them if they were found in my PATH somewhere else.
#NixOS #NixDarwin -
Might be of interest to #Nix users out there:
https://gist.github.com/totoroot/b9684294d599504218e0c655ca56767d
I created a script that helps me audit packages installed vianix profileas I often do that before adding them to my system configuration ❄️
I then tend to forget to remove them after I installed them via my system configuration (as systemPackages or via #HomeManager).
With this script I can later on audit all packages installed, check which binaries they provide and automatically remove them if they were found in my PATH somewhere else.
#NixOS #NixDarwin -
🔍 A riveting saga of transforming your Mac into a pristine museum exhibit with Nix-Darwin, because nothing screams #productivity like a system that stubbornly refuses to change. 🐢🎩 Watch a brave soul dive into the abyss of "imperative rot," only to emerge clutching a manual on how to make your shiny computer behave like an immovable monolith. 💀💻
https://carette.xyz/posts/going_immutable_macos/ #NixDarwin #MacTransformation #TechHumor #TechSaga #HackerNews #ngated -
🔍 A riveting saga of transforming your Mac into a pristine museum exhibit with Nix-Darwin, because nothing screams #productivity like a system that stubbornly refuses to change. 🐢🎩 Watch a brave soul dive into the abyss of "imperative rot," only to emerge clutching a manual on how to make your shiny computer behave like an immovable monolith. 💀💻
https://carette.xyz/posts/going_immutable_macos/ #NixDarwin #MacTransformation #TechHumor #TechSaga #HackerNews #ngated -
🔍 A riveting saga of transforming your Mac into a pristine museum exhibit with Nix-Darwin, because nothing screams #productivity like a system that stubbornly refuses to change. 🐢🎩 Watch a brave soul dive into the abyss of "imperative rot," only to emerge clutching a manual on how to make your shiny computer behave like an immovable monolith. 💀💻
https://carette.xyz/posts/going_immutable_macos/ #NixDarwin #MacTransformation #TechHumor #TechSaga #HackerNews #ngated -
🔍 A riveting saga of transforming your Mac into a pristine museum exhibit with Nix-Darwin, because nothing screams #productivity like a system that stubbornly refuses to change. 🐢🎩 Watch a brave soul dive into the abyss of "imperative rot," only to emerge clutching a manual on how to make your shiny computer behave like an immovable monolith. 💀💻
https://carette.xyz/posts/going_immutable_macos/ #NixDarwin #MacTransformation #TechHumor #TechSaga #HackerNews #ngated -
I'm considering to reinstall my #macOS for the next major OS upgrade. Is there anything I need to be aware of since I'm using #nix / #lix / #nixdarwin and #homeManager?
In my dream world I'd simply tell the installer to do a clean re-install / upgrade, reinstall lix and then pull in my flake from git and do a system-rebuild?
(and ofc restore other stuff and files from my CCC backup)
-
I'm considering to reinstall my #macOS for the next major OS upgrade. Is there anything I need to be aware of since I'm using #nix / #lix / #nixdarwin and #homeManager?
In my dream world I'd simply tell the installer to do a clean re-install / upgrade, reinstall lix and then pull in my flake from git and do a system-rebuild?
(and ofc restore other stuff and files from my CCC backup)
-
I'm considering to reinstall my #macOS for the next major OS upgrade. Is there anything I need to be aware of since I'm using #nix / #lix / #nixdarwin and #homeManager?
In my dream world I'd simply tell the installer to do a clean re-install / upgrade, reinstall lix and then pull in my flake from git and do a system-rebuild?
(and ofc restore other stuff and files from my CCC backup)
-
Bài viết trên blog chia sẻ hành trình tác giả sử dụng Nix để "hồi sinh" một chiếc Pixelbook cũ với NixOS, quản lý MacBook với nix-darwin và tăng cường sức mạnh cho Nix bằng AI để giải quyết một vấn đề tưởng chừng không thể.
#NixOS #NixDarwin #AI #quanlygoi #packageManagement #congnghe #technology
-
Bài viết trên blog chia sẻ hành trình tác giả sử dụng Nix để "hồi sinh" một chiếc Pixelbook cũ với NixOS, quản lý MacBook với nix-darwin và tăng cường sức mạnh cho Nix bằng AI để giải quyết một vấn đề tưởng chừng không thể.
#NixOS #NixDarwin #AI #quanlygoi #packageManagement #congnghe #technology
-
Bài viết trên blog chia sẻ hành trình tác giả sử dụng Nix để "hồi sinh" một chiếc Pixelbook cũ với NixOS, quản lý MacBook với nix-darwin và tăng cường sức mạnh cho Nix bằng AI để giải quyết một vấn đề tưởng chừng không thể.
#NixOS #NixDarwin #AI #quanlygoi #packageManagement #congnghe #technology
-
wohoo 🙌 haven’t had a broken package for like 1w, I was wondering when that was about to happen.
No surprise since I’m on “nixpkgs-unstable” — bleeding edge baby! 🚀
-
wohoo 🙌 haven’t had a broken package for like 1w, I was wondering when that was about to happen.
No surprise since I’m on “nixpkgs-unstable” — bleeding edge baby! 🚀
-
wohoo 🙌 haven’t had a broken package for like 1w, I was wondering when that was about to happen.
No surprise since I’m on “nixpkgs-unstable” — bleeding edge baby! 🚀
-
ffs, here we go again ... goddamn it @nixos_org why can't we just have a smooth transition :blobcatfacepalm:
-
ffs, here we go again ... goddamn it @nixos_org why can't we just have a smooth transition :blobcatfacepalm:
-
ffs, here we go again ... goddamn it @nixos_org why can't we just have a smooth transition :blobcatfacepalm:
-
ffs, here we go again ... goddamn it @nixos_org why can't we just have a smooth transition :blobcatfacepalm:
-
ffs, here we go again ... goddamn it @nixos_org why can't we just have a smooth transition :blobcatfacepalm:
-
Any #nix / #nixpkgs users with #nixDarwin and #homeManager on macOS out there that have an idea how to cleanly uninstall nix-darwin AND home-manager for a flake based setup?
I’d like to switch from Determinate Systems nix installer to the for by #Lix Systems but it seems the only "documented" way to do so is to:
1) uninstall nix-darwin including the home-manager module made changes (so I don't toast my system)
2) uninstall nix via the Determinat uninstall
3) install nix via the Lix Systems installer
4) bootstrap nix-darwin
5) feed it my flake to get my configuration backMy problem is that step 1) is not clearly documented anywhere. There is this part for removing nix-darwin but it doesn't mention how it'll behave if the home-manager module is in use :|
I could use some #help here ’
-
Any #nix / #nixpkgs users with #nixDarwin and #homeManager on macOS out there that have an idea how to cleanly uninstall nix-darwin AND home-manager for a flake based setup?
I’d like to switch from Determinate Systems nix installer to the for by #Lix Systems but it seems the only "documented" way to do so is to:
1) uninstall nix-darwin including the home-manager module made changes (so I don't toast my system)
2) uninstall nix via the Determinat uninstall
3) install nix via the Lix Systems installer
4) bootstrap nix-darwin
5) feed it my flake to get my configuration backMy problem is that step 1) is not clearly documented anywhere. There is this part for removing nix-darwin but it doesn't mention how it'll behave if the home-manager module is in use :|
I could use some #help here ’
