Converting to self-contained standalone?

[QuinnyPig]

I'm not much of a Ruby guy, but I was wondering how much work it would take to port this to something that could be installed via homebrew.

"brew install lunchy" will drive adoption in places that "gem install lunchy" will terrify people (namely: not ruby devs and who remember all too well the nightmare that CPAN wrought on systems). It doesn't seem that it would be too challenging, overall?

[mperham]

Ruby ships with OSX. lunchy should be installable on a vanilla Mac with sudo gem install lunchy. It doesn't get much simpler than that.

What do you suggest instead?

[ivanoats]

also, it's not what the maintainers of home-brew are looking for: see acceptable formulae .

However you might be able to add it to homebrew dupes .

[QuinnyPig]

You're absolutely right. The problem comes in when you have weird rvm setups, users who don't want to install gems on their laptop for a variety of reasons of varying validity[1], and shared mac environments where you want this done locally.

Looking over the homebrew acceptance critera, the only thing that seems to make this ineleigible for inclusion as a formula is the requirements on outside gems. Solutions range from "rewrite the entire thing as a bash script" (which doesn't seem that farfetched, really-- a quick troll through lib/lunchy.rb shows that this is more or less just pattern matching and expansion) to... hmm.

Actually, both of the prerequisites (fileutils and optparse) are shipped as a part of the default Ruby installation on OS X. So technically, if we can either find a way to have lunchy.rb sourced as a part of the binary (not sure on the ruby-isms of this; looks like it'd have to add a specified include path, which can be done as a part of homebrew packaging) or collapsed into the binary itself, then we'd just have to get the homebrew folks to sign off on it. Will talk to them and see what I can do.

[1] "Configuration management systems that can install packages via homebrew but throw up all manner of issues with gem installations" being towards the more valid end of this spectrum

[ivanoats]

Lunchy is so useful that it would be really cool to have it available in homebrew and get wider usage.

It's kinda ridiculous that you'd have to reprogram it in C to get accepted.

On May 26, 2013, at 17:19, Corey Quinn notifications@github.com wrote:

You're absolutely right. The problem comes in when you have weird rvm setups, users who don't want to install gems on their laptop for a variety of reasons of varying validity[1], and shared mac environments where you want this done locally.

Looking over the homebrew acceptance critera, the only thing that seems to make this ineleigible for inclusion as a formula is the requirements on outside gems. Solutions range from "rewrite the entire thing as a bash script" (which doesn't seem that farfetched, really-- a quick troll through lib/lunchy.rb shows that this is more or less just pattern matching and expansion) to... hmm.

Actually, both of the prerequisites (fileutils and optparse) are shipped as a part of the default Ruby installation on OS X. So technically, if we can either find a way to have lunchy.rb sourced as a part of the binary (not sure on the ruby-isms of this; looks like it'd have to add a specified include path, which can be done as a part of homebrew packaging) or collapsed into the binary itself, then we'd just have to get the homebrew folks to sign off on it. Will talk to them and see what I can do.

[1] "Configuration management systems that can install packages via homebrew but throw up all manner of issues with gem installations" being towards the more valid end of this spectrum

—
Reply to this email directly or view it on GitHub.

[QuinnyPig]

I think we can squeak it in.

The challenge I have right now is getting the following inreplace to work:
inreplace 'bin/lunchy', "require 'lunchy'", "require '#{lib}/lunchy'"

That, plus a modern tag on github (so a tarball is generated that I can link against), and I'd say we're in business.

On May 26, 2013, at 8:09 PM, Ivan Storck notifications@github.com wrote:

Lunchy is so useful that it would be really cool to have it available in homebrew and get wider usage.

It's kinda ridiculous that you'd have to reprogram it in C to get accepted.

On May 26, 2013, at 17:19, Corey Quinn notifications@github.com wrote:

You're absolutely right. The problem comes in when you have weird rvm setups, users who don't want to install gems on their laptop for a variety of reasons of varying validity[1], and shared mac environments where you want this done locally.

Looking over the homebrew acceptance critera, the only thing that seems to make this ineleigible for inclusion as a formula is the requirements on outside gems. Solutions range from "rewrite the entire thing as a bash script" (which doesn't seem that farfetched, really-- a quick troll through lib/lunchy.rb shows that this is more or less just pattern matching and expansion) to... hmm.

Actually, both of the prerequisites (fileutils and optparse) are shipped as a part of the default Ruby installation on OS X. So technically, if we can either find a way to have lunchy.rb sourced as a part of the binary (not sure on the ruby-isms of this; looks like it'd have to add a specified include path, which can be done as a part of homebrew packaging) or collapsed into the binary itself, then we'd just have to get the homebrew folks to sign off on it. Will talk to them and see what I can do.

[1] "Configuration management systems that can install packages via homebrew but throw up all manner of issues with gem installations" being towards the more valid end of this spectrum

—
Reply to this email directly or view it on GitHub.
—
Reply to this email directly or view it on GitHub.

[fabn]

Is this dead? It would be so useful to have this as a global command a la heroku

[jamesgecko]

Lunchy has been available in Homebrew's Cask repo for a while.

[vladimyr]

Lunchy has been available in Homebrew's Cask repo for a while.

lunchy-go got migrated from Homebrew Cask to Homebrew (Homebrew/homebrew-cask#86101). Also, lunchy got added to Homebrew, so you can now install this project using:

brew install lunchy

or if you want to use lunchy-go:

brew install lunchy-go