#Dotbot copy file to repo how to

Secondly it would just be another thing for the end-user to learn. First of all it's overkill for something like this. If you want full blown logic you could just write everything in bash or any scripting language yourself and not use dotbot.Д¬reating new config language in my opinion is not a good idea. Logic in config files would be nice but I think there are only few cases where you would want it. You clone/pull the repo and you're ready to install or update. This issue will be used for discussing the design of v2.0.) (This top post will be edited as stuff happens. Should it be on the master branch? Should Dotbot 2.0 forever live in a 2.0 branch with master being reserved for bugfixes for 1.0?

#Dotbot copy file to repo how to

Because people use Dotbot as a submodule, we need to be careful when figuring out how to ship the upgrade.Maybe there are other completely different ways to do it too. What file format do we want to use? There are a couple options I can think of: JSON/YAML file (declarative), other data format (e.g.Make Dotbot usable as a Python library (see #75).Support interactive execution (see #74).Automatic backup / replacement of dotfiles (see #12 and #36).Uninstall command to delete symlinks specified in install config (see #49, 4th item).Be able to write to files/folders that require special privileges (see #49, 3rd item).CLI flag to only run certain sections (see #44 and #49, 2nd item).We'll only switch to the name 'v2.0' if/when we decide to add features that are not backwards compatible. All features that are backwards compatible are being included in Dotbot v1.0 as they are added. This issue is meant for tracking work on Dotbot v2.0, the first major release since v1.0 in March 2014.