> At least on OS X, things are a little easier with Homebrew. Absolutely. I adore Homebrew and it's ecosystem. Cask, in particular, is quite satisfying; gotta love installing a swath of neccessary fonts from the terminal. And, fwiw, the project is about to be on Homebrew, with no tap required: https://github.com/Homebrew/homebrew/pull/49040 Though getting it up was not quite as pain-free than our initial publishes to…
Using npm to distribute a shell script, seriously? That's not such a good idea. I think what you want is something like the Autotools so your software may be installed with the standard './configure && make && make install'. This way, you make it easy for upstream distributions to package your software.
How to Distribute Binaries for OS X Using Homebrew
51–60 of 84 posts
Re: How to Distribute Binaries for OS X Using Homebrew
#52I still use macports; what's the current state of opinion of homebrew vs. fink vs. macports?
Re: How to Distribute Binaries for OS X Using Homebrew
#53I've been forcefully switched to OS X recently because work, and overall it's been pretty great (I view it as a well-integrated UI over FreeBSD). A couple of things drive me nuts though: * (the window manager sucks, but that's not the topic. I had to get it out) * it needs a good package manager For us ol' bearded folk (at least spiritually), OS X comes with a slew of unix tools we love. It already includes both vim…
Homebrew installs in /usr/local, not in /usr, and OS updates never touch /usr/local. And if you're paranoid, you can instruct Homebrew to install somewhere else instead.
Re: How to Distribute Binaries for OS X Using Homebrew
#54Earlier quoted context omitted.
Linux Homebrew[0] can cover it for linux. Just need Windows Homebrew. [0]: https://github.com/Linuxbrew/linuxbrew
Wait, what problem is this solving?
> Can install software to a home directory and so does not require sudo
> Install software not packaged by the native distribution
> Install up-to-date versions of software when the native distribution is old
> Use the same package manager to manage both your Mac and Linux machines
From the "Features" section of the Github.It could also likely be used so make a "safe" Linux distro, where the base system is mounted read only, with a writable home partition.
Re: How to Distribute Binaries for OS X Using Homebrew
#55Re: How to Distribute Binaries for OS X Using Homebrew
#56I've been forcefully switched to OS X recently because work, and overall it's been pretty great (I view it as a well-integrated UI over FreeBSD). A couple of things drive me nuts though: * (the window manager sucks, but that's not the topic. I had to get it out) * it needs a good package manager For us ol' bearded folk (at least spiritually), OS X comes with a slew of unix tools we love. It already includes both vim…
If you like tiling window managers Amethyst is worth checking out. It's a little unpredictable sometimes but otherwise it works well.
Re: How to Distribute Binaries for OS X Using Homebrew
#57Re: How to Distribute Binaries for OS X Using Homebrew
#58Step 1 use pkgsrc . Not joyent's pkgsrc , but real pkgsrc . Step 2 see step 1.
Re: How to Distribute Binaries for OS X Using Homebrew
#59Anyhow, it's nice and simple approach that works.
Re: How to Distribute Binaries for OS X Using Homebrew
#60I've been forcefully switched to OS X recently because work, and overall it's been pretty great (I view it as a well-integrated UI over FreeBSD). A couple of things drive me nuts though: * (the window manager sucks, but that's not the topic. I had to get it out) * it needs a good package manager For us ol' bearded folk (at least spiritually), OS X comes with a slew of unix tools we love. It already includes both vim…
MacPorts is very, umm, opinionated. And doesn't seem to trust anything outside of itself. And has some weird opinions, too.
Example: For some reason, svn is a dependency for nmap. Forgot those gravity waves, the next nobel prize belongs to whoever can figure out why a network scanner depends on an obsolete version control system. So macports installs a shiny new version of svn. Which doesn't play nice with the svn that Xcode uses. Overtime I run (macport) svn from the command line it tells me to upgrade my repository, which breaks the Xcode svn.