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

create and maintain brew tap to install specific vagrant versions #175

Open
hoatle opened this issue Dec 6, 2016 · 3 comments
Open

create and maintain brew tap to install specific vagrant versions #175

hoatle opened this issue Dec 6, 2016 · 3 comments
Assignees
Projects
Milestone

Comments

@hoatle
Copy link
Member

hoatle commented Dec 6, 2016

So that Mac users could use the specified vagrant version to avoid incompatibility issues:

$ brew tap teracyhq/homebrew-tap

and install the specified software versions (virtualbox, vagrant) or the latest ones.

This is required as vagrant 1.9 has problems, we need to use vagrant 1.8 instead for now. When 1.9 is stable enough, we'll upgrade it later with enough testing.

@hoatle
Copy link
Member Author

hoatle commented Jul 20, 2017

@duc4nh could help on this

@hoatle hoatle modified the milestones: v0.5.0-c2-dev, v0.5.0-dev Jul 24, 2017
@hoatle hoatle assigned ducng0610 and unassigned hoatle Jul 24, 2017
@hoatle hoatle assigned hoatle and unassigned ducng0610 Sep 1, 2017
@hoatle hoatle modified the milestones: v0.6.0-a1-dev, v0.6.0-dev Aug 19, 2018
@hoatle hoatle removed the sprt:next label Aug 19, 2018
@hoatle
Copy link
Member Author

hoatle commented Jan 17, 2019

now brew supports switch between different installed package versions, so we can switch vagrant versions easily.

@hoatle
Copy link
Member Author

hoatle commented Jan 17, 2019

brew switch does not work with cask (vagrant, virtualbox), so it's still not convenient to work with different versions.

Currently, I will need to edit the cask tap to install the version I want to use, this is not easy and intuitive for most brew users.

@hoatle hoatle added this to Backlog in public-dev via automation May 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
public-dev
  
Backlog
Development

No branches or pull requests

2 participants