@lfilho I am getting back to trying out your fork of skwp/dotfiles via my own fork of your work. I am looking at it more critically and that has generated some questions.
You seem to be using this repo as more of an all encompassing workstation setup vs. terminal configuration framework like skwp/dotfiles.
Would that be a fair assessment?
I ask this because the Brewfile
seems to install A LOT of stuff that is not terminal related, or is the extra software somehow used by the nvim
plugins.
It really does more than I want and was wondering if I remove most of the stuff from the Brewfile
in my fork if I was going to break a bunch of stuff.
If I chose to modify the Brewfile
and continued to use it on both MacOS
and Linux
what would be the bare minimum Brewfile
without breaking things?
brew 'bat'
brew 'ctags'
brew 'neovim'
brew 'tmux'
brew 'zsh'
I included tmux
above because I compile it on Linux
and do not use the native package anyway.
I was even looking at the possibility of reverting to not even using brew
unless it was on MacOS
and leaving the Brewfile
alone since I install most of that stuff on MacOS
using brew
already. I would probably just create a function in the Rakefile
to install the nvim
requirements if the OS were Linux
.
I don't know, it just seems odd to me to use Homebrew
on Linux
instead of the native package managers that are already there. I'm not sure how I feel about how it creates a whole separate filesystem tree with stuff it installs and that I can end up with Firefox from both native package manager and Homebrew
.
Am I over thinking this?