Skip to content
This repository has been archived by the owner on Dec 2, 2020. It is now read-only.

Request: move Boxen homebrew install to /usr/local #68

Closed
indirect opened this issue Nov 28, 2014 · 15 comments
Closed

Request: move Boxen homebrew install to /usr/local #68

indirect opened this issue Nov 28, 2014 · 15 comments

Comments

@indirect
Copy link

So right now Boxen has a lot of code (that is getting smaller, thanks @dgoodlad!) to work around the way that homebrew very, very strongly expects to be installed into /usr/local. In addition, keeping homebrew in /opt/boxen/homebrew means that it's not possible to use many of the pre-compiled homebrew bottles.

Boxen's readme already makes it clear that it doesn't work with existing homebrew installs in /usr/local, and rubies are already installed outside /opt/boxen (into /opt/rubies).

Since it seems impractical and/or unlikely that puppet-homebrew will ever have even close to as many compiled binaries as homebrew has bottles, can we just move boxen's homebrew into /usr/local and get bottles for everything for free? As a bonus, it would probably then be possible to stop maintaining the entire boxen-install command...

@dgoodlad
Copy link
Contributor

tl;dr: Yes. 😁

Seriously, I have the homebrew package provider open in my editor right now, working on getting the homebrew root configurable with hiera, which I will default to /usr/local.

@indirect
Copy link
Author

🎉🎊🎄

On Thu, Nov 27, 2014 at 7:21 PM, David Goodlad [email protected]
wrote:

tl;dr: Yes. 😁

Seriously, I have the homebrew package provider open in my editor right now, working on getting the homebrew root configurable with hiera, which I will default to /usr/local.

Reply to this email directly or view it on GitHub:
#68 (comment)

@ghost
Copy link

ghost commented Feb 18, 2015

Anticipatory 👏

I look forward to issues like pkrumins/node-png#45 becoming a thing of the past.

@indirect
Copy link
Author

Oh yeah! Is this done yet? @dgoodlad, are you done being hungover after RubyConf AU yet? 😀 (Sorry I didn't manage to say hi! I did see you from across the room and say "hi david" once 😛)

@ghost
Copy link

ghost commented Feb 18, 2015

@indirect you can change boxen_root via facts.d, for example: dd48f30e.

However, when I did this more things broke for me than when I left it as /opt/boxen. I expect this to swing the other way soon enough.

@MikeMcQuaid
Copy link
Contributor

I've been running Boxen's Homebrew in /usr/local for a few months now and it's working great.

@pencil
Copy link

pencil commented Mar 1, 2015

Is there a way to disable the puppet-homebrew bottle monkey patches? I switched to /usr/local using homebrew_root but for some reason end up compiling qt4.

@MikeMcQuaid
Copy link
Contributor

@pencil The monkey patches won't do that; that'll probably be done by Qt trying to build with an option.

@indirect indirect changed the title Request: move Boxen homebrew install to /opt/local Request: move Boxen homebrew install to /usr/local Apr 12, 2015
@MikeMcQuaid
Copy link
Contributor

Closing this out as you can now install into /usr/local and Homebrew's bottles are used.

@kylemclaren
Copy link

@MikeMcQuaid know of an easy way to migrate from /opt/boxen to /usr/local?

@MikeMcQuaid
Copy link
Contributor

@kylemclaren sudo rm -rf /opt/boxen/homebrew /opt/rubies and rerun Boxen.

@kylemclaren
Copy link

@MikeMcQuaid you're a legend, thank you!

@carrchr
Copy link

carrchr commented Feb 21, 2017

wouldn't this command sudo rm -rf /opt/boxen/homebrew /opt/rubies nuke all the stuff you've downloaded/installed into home-brew and require re-installing it all? Are you supposed to mv /opt/boxen/homebrew /usr/local/homebrew first?

@MikeMcQuaid
Copy link
Contributor

wouldn't this command sudo rm -rf /opt/boxen/homebrew /opt/rubies nuke all the stuff you've downloaded/installed into home-brew and require re-installing it all?

yes

Are you supposed to mv /opt/boxen/homebrew /usr/local/homebrew first?

no; you cannot move things around like this as paths are hardcoded in binaries.

@carrchr
Copy link

carrchr commented Feb 21, 2017

okay. thank you for the clarification

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

No branches or pull requests

6 participants