help with porting vagrant

Nikolai Lifanov lifanov at mail.lifanov.com
Wed Apr 24 14:11:21 UTC 2013


On 04/24/2013 10:08 AM, Nikolai Lifanov wrote:
> On 04/24/2013 10:02 AM, Thibaut DELOFFRE wrote:
>> Hello,
>> 
>> You need to install rugygems and:
>> 
>> $ gem fetch vagrant $ gem unpack vagrant $ 'your work here'
>> 
>> You're welcome
>> 
>> Thibaut
>> 
>> 
>> On Wed, Apr 24, 2013 at 3:54 PM, Nikolai Lifanov 
>> <lifanov at mail.lifanov.com <mailto:lifanov at mail.lifanov.com>> 
>> wrote:
>> 
>> Hello.
>> 
>> I am trying to port Vagrant (http://vagrantup.com/) and I hit 
>> somewhat of a wall. I want to use all of the rubygem magic in 
>> bsd.ruby.mk <http://bsd.ruby.mk>, but I need to build the gem 
>> first ("gem build vagrant.gemfile"). It seems that I can't
>> override the DISTNAME or EXTRACT_SFX if I want to use
>> USE_RUBYGEMS, and it needs to be downloaded from GH as a
>> .tar.gz.
>> 
>> How can I fetch/extract/build a rubygem and then use the logic in
>>  bsd.ruby.mk <http://bsd.ruby.mk> to install it cleanly?
>> 
>> Thank you! _______________________________________________ 
>> freebsd-ruby at freebsd.org <mailto:freebsd-ruby at freebsd.org>
>> mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To 
>> unsubscribe, send any mail to
>> "freebsd-ruby-unsubscribe at freebsd.org 
>> <mailto:freebsd-ruby-unsubscribe at freebsd.org>"
>> 
>> 
> 
> But here is the problem: vagrant stopped shipping as a gem since
> 1.1.x http://mitchellh.com/abandoning-rubygems 
> http://rubygems.org/gems/vagrant
> 
> However, it still uses rubygems and bundler together to create the
> "installer". So I need to first build the gem and then install the
> gem. _______________________________________________ 
> freebsd-ruby at freebsd.org mailing list 
> http://lists.freebsd.org/mailman/listinfo/freebsd-ruby To
> unsubscribe, send any mail to
> "freebsd-ruby-unsubscribe at freebsd.org"
> 

To be more specific: I can install it alright, but I would like to
create a port of it and I would like help with how to reuse the
USE_RUBYGEM logic without stuffing a lot of it into the port Makefile
if I actually have to make the gem first.



More information about the freebsd-ruby mailing list