Configurable tools
Pulls out the tool configuration in a YAML file under config.
Also makes all constant values (CACHE_DIR, ZIP_EXE etc.) overridable through environment variables (which you can use on the rake command line)
Updates all software to the latest versions.
Not ready yet, PR opened to be able to clarify a few things
Q1: What are you doing with that 'includes' parameter?
That Appveyor build is going to block forever because it's asking for the git name and email
Torben I need your input here, there's a few things that do not work due to environment scripts:
- Asking for the name and email for git in set-env blocks all builds.
- Atom plugin installation fails.
On the other hand I've restructured most of the Rakefile so that we can use it as a basis for all devpacks and handle exceptions (like the double unpack for Chef).
Basically I broke the kitchen and took home the oven to bake my own cookies.
@damphyr while I believe we could get this to work / pass the appveyor build again, I'm not sure what to do with it.
Instead of doing something half-assed, I'd rather focus on making https://github.com/Zuehlke/z-devpack reusable / modular enough (see https://github.com/Zuehlke/z-devpack/issues/1) so it can be the new basis for bills-kitchen.
What do you think?
What I think is : https://github.com/Zuehlke/z-devpack :)
Do we scrap this or should I bring it up to date?
I should probably add some large banner stating that this is unmaintained (ever since I switched to macOS about 1.5 years ago...)
I'm currently maintaining https://github.com/tknerr/linus-kitchen/ instead, which is a Linux Developer VM variant with the same intent / goal as Bill's Kitchen.
So yes, I'm in favor of ditching this, unless someone wants to continue to maintain it