Change the default OSX package manager to Macports

[mpapis]

As requested by Homebrew team in Homebrew/legacy-homebrew#19454 (comment) and Homebrew/legacy-homebrew#19454 (comment) RVM will no more automatically call Homebrew installer.

To keep the automation the default will be switched to Macports.

This ticket is scheduled after #1833.

[mpapis]

@CodeGnome I heard you use both Macports and RVM, is that true? Any chance you could try:

rvm get head
rvm autolibs macports
rvm requirements ruby-head

also I think we might use some code to update outdated packages, any examples of checking for outdated / upgradable packages?

[todd-a-jacobs]

@mpapis I do. Let me give it a shot, and report back. Do I need to blow away my current RVM install for the test to be valid for your purposes?

As for updates, the usual MacPorts ceremony is:

sudo port selfupdate
sudo port upgrade outdated

I assume you want to have me run that after updating the the latest RVM head, and check for...what?

[mpapis]

no just show me the outputs ... best would be test on a fresh machine, but I will take care of that before switching the default.

[todd-a-jacobs]

@mpapis I ran a fresh install after removing the ~/.rvm folder, but several things fail. First:

/Users/codegnome/.rvm/scripts/functions/osx-ssl-certs: line 11: : No such file or directory
/Users/codegnome/.rvm/scripts/functions/osx-ssl-certs: line 12: : No such file or directory

Second, no rubies are installed, either during initial installation when passed the --ruby flag, or when calling rvm install directly. A full transcript has been emailed to you.

[envygeeks]

Port that into a ticket of it's own please @CodeGnome so it can be tracked. Thanks!

[todd-a-jacobs]

@envygeeks What should be a separate ticket? I didn't see anything that wasn't related to the MacPorts install issue. I'd be happy to create a separate ticket if you tell me what you think is an unrelated issue.

[envygeeks]

@CodeGnome The errors you got while installing or directly after. It's not that they are unrelated it's better for tracking that they put into their own tickets. Of course clearly fine if you don't want to but it just makes it easier to track what's what when it comes down to tracking.

[mpapis]

fixed, but as @envygeeks mentions - it's better to have separate tickets per every issue, anyway thanks for catching the problem

[AJ-Acevedo]

Homebrew and MacPorts typically don't play well together. If a user already has Homebrew installed, having RVM automatically installed via RVM can cause unexpected behavior and in my opinion, is not desired.

[mpapis]

@AJ-Acevedo the default is used after auto detection fails, RVM will check first if any of the supported managers is installed and only fallback to MacPorts if none is available, you would know that if you checked the code => https://github.com/wayneeseguin/rvm/blob/47dcc36e6861e273dab4d8d693802208d1e7ad78/scripts/functions/requirements/osx

[jessmartin]

@mpapis I'm sad the the homebrew team insisted on switching the default to macports. I understand that you guys needed to do it. However, before I came to github to check things out, I was surprised when macports started getting installed on my vanilla Mac. Maybe the default package manager should be documented somewhere other than just this ticket? I didn't see it on the website or the github readme. Thanks!

[mpapis]

both https://rvm.io/rvm/autolibs and rvm help autolibs are updated with the autodetection information

[jessmartin]

Thanks!

On Friday, May 31, 2013, Michal Papis wrote:

both https://rvm.io/rvm/autolibs and rvm help autolibs are updated with
the autodetection information

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/1840#issuecomment-18753419
.

Jess Martin
http://jessmart.in