3 ms·

`brew install sl` if you want it on OS X.

by Oompa 16y ago

philwelch 16y ago
`[sudo] port install sl` works too, if you're still on MacPorts.
- heatdeath 16y ago
  "Still on" and intend to stay on.
  - philwelch 16y ago
    Me too, which is why I investigated this.
  - masklinn 16y ago
    You and me both, still fighting the good fight \n/
- Lewisham 16y ago
  Somewhat off-topic, but why are people advocating Homebrew over MacPorts? I've never found a port I thought should have been in MacPorts not being there, `sudo port -v install [package]` always seems to work, and dependencies are automagically followed. Looking at the website, it seems the general "improvement" is that you can edit formulas before you install; but that's exactly why I use MacPorts! I don't want to know how to install all these things, that abstraction is something I prefer. If you don't intend to do this, is Homebrew really any different?
  - callahad 16y ago
    Homebrew tries to coexist with the pre-existing environment, whereas MacPorts and Fink create their own little isolated hierarchies in /opt and /sw, respectively. Which means that if install Git, that's all I get. With Macports, I'll also be installing duplicate versions of at least curl, openssh, and rsync, as per http://help.github.com/mac-git-installation/ http://help.github.com/mac-git-installation/
    - ant5 16y ago
      Which is a nice-sounding idea until the OS components are growing stale, at which point you'll be wondering why, for instance, your scripting language of choice's hash libraries don't support the modern idea of SHA256 (the answer being: because the OpenSSL version shipped with OS X was too old), or why your builds are now failing (because Apple shipped a library update without updating the headers in a Software Update). Homebrew tries to take the high ground here, but it's just naivety. They'll wind up installing "duplicate" versions of software too -- in fact, they already are doing so. The short-cycle of Leopard -> Snow Leopard won't be happening again soon, and the only alternative to adding "duplicate" software to your dependency tree is letting software go stale (for example: python 2.7 vs SL's 2.6.1). It's easy to say that the 10 years of knowledge that both MacPorts and Fink have about the platform is "stupid" when you haven't had the experience of maintaining a working packaging/port system through a few OS X release cycles, and aren't familiar with the problem space or Apple's policies.
      - jackolas 16y ago
        Exactly, I use homebrew occasionally, but its really a pain because it doesn't keep its python libs in its prefix fr example. If you use non-system stuff it's a real pain in the ass.
  - ant5 16y ago
    > Looking at the website, it seems the general "improvement" is that you can edit formulas before you install; but that's exactly why I use MacPorts! I don't want to know how to install all these things, that abstraction is something I prefer. You can edit the MacPorts portfiles too, if you want to: sudo port edit <portname> I don't really understand why people are advocating Homebrew. The only real advantage seems to be the smaller dependency tree achieved by relying on Apple's shipped components, but that's a short-term band-aid that isn't going to last.

`brew install sl` if you want it on OS X.

by Oompa 16y ago

`brew install sl` if you want it on OS X.

philwelch 16y ago

`[sudo] port install sl` works too, if you're still on MacPorts.

heatdeath 16y ago
"Still on" and intend to stay on.
- philwelch 16y ago
  Me too, which is why I investigated this.
- masklinn 16y ago
  You and me both, still fighting the good fight \n/
Lewisham 16y ago
Somewhat off-topic, but why are people advocating Homebrew over MacPorts? I've never found a port I thought should have been in MacPorts not being there, `sudo port -v install [package]` always seems to work, and dependencies are automagically followed. Looking at the website, it seems the general "improvement" is that you can edit formulas before you install; but that's exactly why I use MacPorts! I don't want to know how to install all these things, that abstraction is something I prefer. If you don't intend to do this, is Homebrew really any different?
- callahad 16y ago
  Homebrew tries to coexist with the pre-existing environment, whereas MacPorts and Fink create their own little isolated hierarchies in /opt and /sw, respectively. Which means that if install Git, that's all I get. With Macports, I'll also be installing duplicate versions of at least curl, openssh, and rsync, as per http://help.github.com/mac-git-installation/ http://help.github.com/mac-git-installation/
  - ant5 16y ago
    Which is a nice-sounding idea until the OS components are growing stale, at which point you'll be wondering why, for instance, your scripting language of choice's hash libraries don't support the modern idea of SHA256 (the answer being: because the OpenSSL version shipped with OS X was too old), or why your builds are now failing (because Apple shipped a library update without updating the headers in a Software Update). Homebrew tries to take the high ground here, but it's just naivety. They'll wind up installing "duplicate" versions of software too -- in fact, they already are doing so. The short-cycle of Leopard -> Snow Leopard won't be happening again soon, and the only alternative to adding "duplicate" software to your dependency tree is letting software go stale (for example: python 2.7 vs SL's 2.6.1). It's easy to say that the 10 years of knowledge that both MacPorts and Fink have about the platform is "stupid" when you haven't had the experience of maintaining a working packaging/port system through a few OS X release cycles, and aren't familiar with the problem space or Apple's policies.
    - jackolas 16y ago
      Exactly, I use homebrew occasionally, but its really a pain because it doesn't keep its python libs in its prefix fr example. If you use non-system stuff it's a real pain in the ass.
- ant5 16y ago
  > Looking at the website, it seems the general "improvement" is that you can edit formulas before you install; but that's exactly why I use MacPorts! I don't want to know how to install all these things, that abstraction is something I prefer. You can edit the MacPorts portfiles too, if you want to: sudo port edit <portname> I don't really understand why people are advocating Homebrew. The only real advantage seems to be the smaller dependency tree achieved by relying on Apple's shipped components, but that's a short-term band-aid that isn't going to last.