Tested with Mac OSX Mavericks on a late 2011 MBP
My testing approach has been to erase a partition and install fresh Mavericks onto it. Run the scripts, tweak and then tear down and reinstall on the partition.
- if bork doesn't stop for errors, it should probably aggregate them and output post-flight
- output can be very noisy if running scripts comingled (maybe I shouldn't be doing that though)
- confused about what ok destination does in conjunction with ok symlink
- at least on my system, it doesn't set where the symlink should end up and I've had to manually specify the path
ok brewby itself doesn't install brew (though looking at the source, this bit appears to be commented out). It does check for it's presence though, once installed.
- I'd love to have a generic way to run a task that just looks for 0 or non-0 exits and cleans up the output (could go toward making the output less noisy when it's appropriate to drop to scripting)
- what do you think about an scutil type (setting hostname is all I'm currently doing)?
Overall using bork has been very pleasant and straightforward. Thanks for the work :)
Understood on 1-5
ok execandok scutilas you describe are exactly what I'd want :)Thanks again for bork, it's been a pleasure to work with!