6 ms·

Can you explain exactly what you are describing: “it doesnt deal well with multiple versions at the same time” Also what system/os are you comparing to?

cies 6y ago
Nix(OS)?
capableweb 6y ago
Don't have a ton of experience with either macports or homebrew but pretty much any package manager deals with running multiple different versions at the same time, or projects using different versions of the same dependency, without getting in your way. Biggest/most famous example I guess would be javascript/npm/npm inc registry.
- masklinn 6y ago
  Nope, completely different “package manager”. Homebrew and Mac ports are more similar to apt or yum or Pacman, and those often do not provide for running multiples of the same software except in specific edge cases where sauf software can be argued to be different from itself e.g. python2/3, they sort of things.
ragnese 6y ago
Probably comparing it to MacPorts, which does allow multiple versions of the same packages to be installed simultaneously.
nicolas_t 6y ago
I'm comparing to macports. I remember a brew update that removed an old version of openssl causing all of my older ruby packages to fail. Now I would definitely not use ruby 1.9.x in production but I sometimes do have to be able to run locally antique codebases that haven't been used in a long time. I was caught off guard because a simple install of an unrelated application with homebrew destroyed a big part of my work flow. Macports never did this and kept libraries side by side cleanly. Now, this is from the point of view of a software developer with a specific niche requirement. For normal users, from a security standpoint, it would most likely make sense to remove old versions of openssl.
- cutler 6y ago
  Why not just use rbenv with a $HOME/.gem directory. Much simpler as Ruby versions come with their own openssl.
  - nicolas_t 6y ago
    I was using rbenv, but try installing an ancient version of ruby through rbenv, I have never been able to get it to work without having the existing openssl library in my system (not an issue with newer versions)
    - cutler 6y ago
      I think that's because rbenv only introduced bundling openssl libs at a certain point in its history so, yes, if you're going for a really old version fair point.

cies 6y ago

Nix(OS)?

capableweb 6y ago

Don't have a ton of experience with either macports or homebrew but pretty much any package manager deals with running multiple different versions at the same time, or projects using different versions of the same dependency, without getting in your way. Biggest/most famous example I guess would be javascript/npm/npm inc registry.

masklinn 6y ago
Nope, completely different “package manager”. Homebrew and Mac ports are more similar to apt or yum or Pacman, and those often do not provide for running multiples of the same software except in specific edge cases where sauf software can be argued to be different from itself e.g. python2/3, they sort of things.

ragnese 6y ago

Probably comparing it to MacPorts, which does allow multiple versions of the same packages to be installed simultaneously.

nicolas_t 6y ago

I'm comparing to macports. I remember a brew update that removed an old version of openssl causing all of my older ruby packages to fail. Now I would definitely not use ruby 1.9.x in production but I sometimes do have to be able to run locally antique codebases that haven't been used in a long time. I was caught off guard because a simple install of an unrelated application with homebrew destroyed a big part of my work flow. Macports never did this and kept libraries side by side cleanly. Now, this is from the point of view of a software developer with a specific niche requirement. For normal users, from a security standpoint, it would most likely make sense to remove old versions of openssl.

cutler 6y ago
Why not just use rbenv with a $HOME/.gem directory. Much simpler as Ruby versions come with their own openssl.
- nicolas_t 6y ago
  I was using rbenv, but try installing an ancient version of ruby through rbenv, I have never been able to get it to work without having the existing openssl library in my system (not an issue with newer versions)
  - cutler 6y ago
    I think that's because rbenv only introduced bundling openssl libs at a certain point in its history so, yes, if you're going for a really old version fair point.