This message was deleted.

sparse-intern-71089

08/14/2019, 8:28 PM

This message was deleted.

white-balloon-205

08/14/2019, 8:29 PM

We are actively discussing that right now. Either way, we will almost certainly create our own tap, but we want to keep things as simple for end users as possible here as we know many users depend on HomeBrew for getting Pulumi.

cool-egg-852

08/14/2019, 8:37 PM

Ok. I think you can have a the same formula in multiple taps. It’ll just use whatever is newer. So for those who need/want more up to date versions, a custom tap solves that. I do see the active discussion, just didn’t sound like they were going to be too supportive.

white-balloon-205

08/14/2019, 8:41 PM

Thanks - yeah - that's generally what we're expecting to do here. @bitter-oil-46081 is looking into a custom tap right now to make it easier for folks to get access to the

1.0.0-beta

releases we've started to put out.

cool-egg-852

08/14/2019, 8:43 PM

Cool. Looking forward to upgrading.

bitter-oil-46081

08/14/2019, 10:25 PM

Looking into it, it appears that if you have the same formula in both homebrew core and a tap then

brew install

and

brew upgrade

still prefer the version in homebrew core vs the tap, so we'll have to figure something else out.

bitter-oil-46081

08/14/2019, 11:43 PM

Ahh, but if you explicitly jump over to one that comes from a tap, then later commands like

brew upgrade pulumi

seem to pick that up.

fierce-dinner-20116

08/15/2019, 7:54 PM

I still think a tap would be preferable. It takes a while for homebrew to merge in updates (sometimes days)

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.