I was wondering what if we could develop some common dotfiler plugins. They can be same dotfiler-oriented repositories, but they will have scripts for common tasks and dotfiler users can reuse it.
For example, when i start creating dotfiles repos, i found myself wanting to have some commands for bootstrapping my environment on some machines. For example, i made simple stupid [script](https://github.com/l0kix2/dot-homebrew/blob/master/.scripts/brew-install-packages.sh script) for installing my homebrew packages. It installs in ~/.scripts directory and assumes, that i have brew package names in ~/.brew/* text files.
As downside this common scripts must be shell-agnostic, but in simple cases, i think it will not be so hard.
At bottom line we will have some common scripts, gently forcing some directories naming conventions, but it sure will be user choice and plugins are simple dotfiler repos, so we don't have to invent anything new (maybe some syntax sugar for dot executable). So user can benefit from already invented and community-developed ways of doing common environment-bootstrap-related tasks.
Any thoughts on this? I can explain better in russian, if it is not clear because of my loosy english.
I was wondering what if we could develop some common dotfiler plugins. They can be same dotfiler-oriented repositories, but they will have scripts for common tasks and dotfiler users can reuse it. For example, when i start creating dotfiles repos, i found myself wanting to have some commands for bootstrapping my environment on some machines. For example, i made simple stupid [script](https://github.com/l0kix2/dot-homebrew/blob/master/.scripts/brew-install-packages.sh script) for installing my homebrew packages. It installs in
~/.scriptsdirectory and assumes, that i have brew package names in~/.brew/*text files. As downside this common scripts must be shell-agnostic, but in simple cases, i think it will not be so hard.At bottom line we will have some common scripts, gently forcing some directories naming conventions, but it sure will be user choice and plugins are simple dotfiler repos, so we don't have to invent anything new (maybe some syntax sugar for
dotexecutable). So user can benefit from already invented and community-developed ways of doing common environment-bootstrap-related tasks.Any thoughts on this? I can explain better in russian, if it is not clear because of my loosy english.