> On Saturday, February 12, 2011, Mikel Lindsaar <[email protected]> wrote: >> On 12/02/2011, at 1:56 PM, Joshua Partogi wrote: >>> I have a rubygem and would like to include another gem as dependency. >>> Unfortunately that gem that I want to include has not been released to >>> rubygems.org and still in github. Is it possible to include this gem >>> in gemspec? >> >> You can include it via Bundler as Chris and Ivan has suggested, but it won't >> be listed as a gem dependency in rubygems. >> >> ie, having it in the gem file, means you could go into the installed gem >> directory and type "bundle install" to install all the gems you need, but >> the dependent gems listed this way will not be installed when you do a "gem >> install yourgem" which I think is your expected behaviour. >> >> A "simple" solution, is fork the git repo, make a gem of the code and >> publish it as "yourname-gemname" and depend on that until an "official" >> version is released. On 12/02/2011, at 8:24 PM, Joshua Partogi wrote: > Thanks for the advise. Would that be considered a dirty approach > because you are thrashing rubygems.org? Please advise.
As a gem owner, I don't think so. As long as you didn't try and release it as the original gem name. Of course, the other option is go ahead and release it as the original gem name after contacting the author. Tell him or her that you need the code as a gem, that you are happy to do the work to make it a gem and publish it, and then set them as a co-author of the gem. That way they can stay in control. Mikel -- You received this message because you are subscribed to the Google Groups "Ruby or Rails Oceania" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en.
