Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Brewfiles #175

Closed
kevinSuttle opened this issue Dec 5, 2013 · 9 comments
Closed

Brewfiles #175

kevinSuttle opened this issue Dec 5, 2013 · 9 comments

Comments

@kevinSuttle
Copy link

It'd be great to refactor to support this. If I get time, I'll do it, but that's a big if. https://coderwall.com/p/afmnbq

Hopefully someday Caskfiles will be a thing too. Homebrew/homebrew-cask#1946

@philoserf
Copy link

@kevinSuttle

The Brewfile handles casks natively. Here is a fragment from my own Brewfile.

...
# casks
install brew-cask
tap phinze/cask
cask install antirsi
...

@kevinSuttle
Copy link
Author

Ah, good to know! I'd still like to see the Homebrew packages refactored to use the Brewfile format though.

@kevinSuttle
Copy link
Author

Apparently you can split up multiple Brewfiles to organize them also.

$ echo 'install ruby' > Brewfile-ruby
$ echo 'bundle Brewfile-ruby' > Brewfile
$ brew bundle

See comments: https://coderwall.com/p/afmnbq/

@kevinSuttle
Copy link
Author

My fork/branch is currently very different as I move away from needing Ruby, but the setup is similar (based on Brewfiles).

https://github.com/kevinSuttle/laptop/tree/brewfiles

@croaky
Copy link
Contributor

croaky commented Mar 17, 2014

What's the upside of using the Brewfile in the case of the laptop script? One downside I see is that the generated mac file is no longer human-readable as a single place to see what gets installed. I have to jump to the Brewfile.

I noticed I have a lot of the things you install that aren't in laptop yet, though!

  • node
  • alfred
  • bartender
  • dropbox
  • google-chrome
  • kindle
  • rdio
  • sizeup

The casks in particular have some great apps.

@kevinSuttle
Copy link
Author

The upside for me is encapsulation, but human readability is important for sure. I'm also happy to have all of my binaries and open source artifacts (fonts, QuickLook plugins) in one place. It could be a single point of failure, or a single point of success. :) It's opinionated for sure, but it's also about hopefully encouraging the convention of the Brewfile, like the Gemfile, Makefile, etc.

@croaky
Copy link
Contributor

croaky commented Mar 17, 2014

Gotcha. I definitely agree with you about encouraging the Brewfile convention. I guess I think of it as more project-specific like a Gemfile ("this project needs Postgres, Redis, and ImageMagick) than meant for the whole machine. I think I also prefer the tradeoff of being slightly more explicit in the laptop script than the encapsulation (but I also see your point there).

I'm going to close this issue but it made me want to open #210 to introduce a ~/.laptop.local convention where personalizations can happen. I already stole a bunch of your brew casks into my ~/.laptop.local:

https://github.com/croaky/dotfiles/blob/master/laptop.local

@croaky croaky closed this as completed Mar 17, 2014
@kevinSuttle
Copy link
Author

Haha, nice. Thanks Dan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants