I contemplated doing that (something like the brew-cask syntax), but it ended up not really being worth the complexity, especially when you consider that not all of the commands necessarily correlate to those in Homebrew (e.g. setting defaults). Might consider doing something like that in the future though, if it ends up that people aside from me want this.
It's also worth noting that even projects such as Homebrew Cask are also merely extensions to Homebrew (AFAIK, there aren't any plans of it getting merged in anytime soon).
Right now it's updated whenever you install something with cider. You can update it with whatever you currently have installed using `cider [cask] missing`. Defaults are the same way - cider supports the same syntax as the `defaults` command, so you should be able to use it as a drop-in replacement in most cases.
It will install cask for you, but homebrew needs to be installed via the script on http://brew.sh/#install (you also need to have Xcode or Apple's cli tools installed).
I actually tried mackup a few weeks ago and had to wipe my machine because it messed up my settings so much (who would've thought backup could be such a dangerous command?)
Cider's approach is much safer since all it does is reinstall the components & settings you've specifically allotted it to. Rather than move all your various configs and caches around in an attempt to keep them in sync (which is, IMO, subject to headaches and not worth the hassle), the whole point of Cider is to keep as little state on your machine as possible so you can stop thinking about this stuff.
There was once a similar project also called Cider, created by Corey Donohoe (atmos) from GitHub. It was renamed to cinderella because of trademark infringement, so you might want to check that out: https://github.com/atmos/cider
21 comments
[ 5.4 ms ] story [ 66.3 ms ] threadI understand why things proliferate like this but it can be frustrating.
It's also worth noting that even projects such as Homebrew Cask are also merely extensions to Homebrew (AFAIK, there aren't any plans of it getting merged in anytime soon).
But seriously, I really like this idea. You should definitely PR this into Homebrew though.
Symlinks and scripts are manual, but I plan on changing that: https://github.com/msanders/cider/issues/3
Edit: pretty sure I fixed the bug - could you verify by trying the version on master?
I'm asking, because I am in the process of creating an Ansible playbook (http://docs.ansible.com/homebrew_module.html and http://docs.ansible.com/homebrew_cask_module.html) and I want to write a small bootstrap script to install homebrew and homebrew cask first.
Cider's approach is much safer since all it does is reinstall the components & settings you've specifically allotted it to. Rather than move all your various configs and caches around in an attempt to keep them in sync (which is, IMO, subject to headaches and not worth the hassle), the whole point of Cider is to keep as little state on your machine as possible so you can stop thinking about this stuff.
But what if I use Homebrew to install a package (pyenv) to manage my Pythons to install cider to bootstrap Homebre...
StackOverflowException thrown. Comment aborted.