In that case, if everything works out the way I like, I can repeat the installation easily on another system. So I try to automate as many of the steps as reasonably possible, and document all the other stuff. Simple I want the installation to be working, automated and minimal. Enought to get me started… Why a dot-files repository? Some automated installation scripts even hinted at the possibility of using it all on a MacBook. The setup with a tiling window manager seemed like an interesting configuration, useful for development. Of course, there is Homebrew, but then Apple releases a system update which messes up all permissions where Homebrew is installed… And don’t get me started about having to install some gigabytes of Xcode, just because you need a C compiler.Īnd so at some point I came across the dot-files of Jessie Frazelle. For example Bash and Git versions are lagging behind, missing all the new features. I had and have the feeling it’s becoming more mainstream, more like iOS and, less like a system for professional users like developers. It started some time before that, with not being totally content the way Apple is developing its macOS operating system. If you don’t believe me, see the commits in the GitHub repository. The reason why I started this ‘adventure’ lies before the announcement of the new MacBook Pro. The “how” you can find in the debian_install.md file in my GitHub repo.

Why? Those are the questions I’m hoping to answer in this blog post.

I’m writing this in Neovim, inside RXVT, in the i3 window manager, on Debian, running on a MacBook Pro (2015 model).

Arch linux macbook pro 2015