Live data from Hacker News

Osxc – Simple configuration tool for OS X

osxc.github.io

21–30 of 45 posts

Re: Osxc – Simple configuration tool for OS X

#22
post #15

The osxc website and documentation is riddled with basic grammar and spelling errors and incorporates slang like "osxc got your back". That doesn't inspire much confidence. Edit: Wow with the downvotes. I'm just offering feedback in a polite manner for what a lot of others are probably thinking.

Just because this is a software not an English book.

Re: Osxc – Simple configuration tool for OS X

#23
This is neat. I think it'd be pretty awesome if it were possible to download all the dmg's/installers/apps in a folder/drive without installing them so at a later date you could a) install everything without having to wait hours to download or require an internet connection and b) keep your packages up to date (almost as a backup) running the script every once in a while to make sure you have the most up to date packages/installers.

Re: Osxc – Simple configuration tool for OS X

#24
post #23

This is neat. I think it'd be pretty awesome if it were possible to download all the dmg's/installers/apps in a folder/drive without installing them so at a later date you could a) install everything without having to wait hours to download or require an internet connection and b) keep your packages up to date (almost as a backup) running the script every once in a while to make sure you have the most up to date pack…

Puppet (and Boxen for help on OSX) can do this for you with appdmg package provider: http://docs.puppetlabs.com/references/latest/type.html#packa...

Re: Osxc – Simple configuration tool for OS X

#25
post #24
post #23

This is neat. I think it'd be pretty awesome if it were possible to download all the dmg's/installers/apps in a folder/drive without installing them so at a later date you could a) install everything without having to wait hours to download or require an internet connection and b) keep your packages up to date (almost as a backup) running the script every once in a while to make sure you have the most up to date pack…

Puppet (and Boxen for help on OSX) can do this for you with appdmg package provider: http://docs.puppetlabs.com/references/latest/type.html#packa...

Nice. I'd love to see templates so you can easily customize depending on what kind of environment you want so you can start from zero. E.g. 1. Development 2. Design 3. Engineering 4. Management 5. General use

It's probably just me, but it seems like all of these require too much investment time before you have something usable for future use (replicating your current environment).

Which brings me to this, how about a script that analyzes what you already have installed and creates this set up for you which you can customize to easily add/remove packages/apps/installers using Boxen and similar? Anyone know of such tools? My MBP is full of crud after using SuperDuper!/Time Machine for several years to start new macbook setups and installing new versions of OS X on top of the old OS.

Re: Osxc – Simple configuration tool for OS X

#26
post #5

Earlier quoted context omitted.

because writing yaml is way easier than writing a bash script.

This yaml approach requires me to know a lot more about existing software than the bash script does. I will need to: - Read up on the documentation for osxc or battle school - Look at other configuration files to get a feel for what mine needs to look like. - Learn about the differences between playbooks or recepies or what have you. - Download some proprietary software that I will likely never use again. This is all…

The way my brain works, I’d rather update yaml files than debugging shell script. And because I obsess over this stuff anyway, osxc looks quite appealing.

Re: Osxc – Simple configuration tool for OS X

#27
post #9

For some reason I'd never seen Homebrew Cask before, which looks very interesting! Does anyone have experiences with Cask to share?

Homebrew Cask is awesome! A couple of weeks ago I decided to backup my hard drive, reformat it and reinstall OS X Mavericks to get rid of the cruft that seems to have built up in 4 years, updating from every OS since Mac OS X 10.5 Leopard. I made halfhearted attempts to organize my dotfiles and configuration in the past, like the cool kids do on Github. That’s when I learned about Homebrew Cask ( http://caskroom.io )…

I'm hoping someone could answer this for me. How do you trust the applications that `brew cask` installs?

What is preventing `brew cask install firefox` from installing something malicious? When I download an application manually, I trust the site I'm on by virtue of being there and being savvy enough to know it's a legitimate site. But when you script it, you lose the ability to gauge see for yourself what you're downloading.

I realize I could probably do: `brew cask info firefox`, find the ruby file it points to (https://github.com/caskroom/homebrew-cask/commits/master/Cas...), open that up, verify the link is trustworthy.. but I don't want to do that for every installation. And if it's valid now, what's to prevent it from changing in the future?

How do you guys justify using cask?

Re: Osxc – Simple configuration tool for OS X

#28
post #15

The osxc website and documentation is riddled with basic grammar and spelling errors and incorporates slang like "osxc got your back". That doesn't inspire much confidence. Edit: Wow with the downvotes. I'm just offering feedback in a polite manner for what a lot of others are probably thinking.

You were probably downvoted because your feedback was not given in a polite manner.

Re: Osxc – Simple configuration tool for OS X

#29

For some reason I'd never seen Homebrew Cask before, which looks very interesting! Does anyone have experiences with Cask to share?

Cask could be awesome, but it's not at this stage. There are no upgrades, in many cases it doesn't work. Most apps complain that they are not in /Applications, but are in ~/Applications instead and so on. At the end of the day, it duplicates some of the Homebrew functionality - some non-GUI packages are getting into Cask, because possibly Homebrew doesn't want them - it's a bit confusing as well. I think efforts should be put into merging into Homebrew instead of keeping it separate.
Post reply on HN