Re: UPDATE: devel/ruby-bundler to 1.3.5

2013-05-06 Thread Mikolaj Kucharski
On Sun, Apr 28, 2013 at 08:26:10AM -0700, Jeremy Evans wrote:
 On Sun, Apr 28, 2013 at 3:01 AM, Mikolaj Kucharski
 miko...@kucharski.namewrote:
 
  I've tried and no joy -- regress is not happy, and regress is doing here
  some really invasive stuff, which will probably fail with systrace
  (untested). I'm attaching the output from make test. Also, below patch
  contains my debugging patches, which should probably be removed, but I
  kept them, so someone more experienced with Ruby and Ruby ports could
  have a look what should be done with that part of code, if anything
  actually needs to be done.
 
 
 Most of the remaining failures are due to other programs not being
 found because of their extension (ruby/rackup/rake).  You could
 probably fix this by adding them to post-extract.
 
 The regress tests should probably be commented out by default,
 since they are downloading gems.
 
 Are you upgrading bundler because a dependency requires a newer
 version, or just to get the most current version?  In either case, have
 you verified the existing dependencies are OK with the newer version?
 
 Jeremy

To get the most current version. I got a bit out of practice in ports
and I never had a chance to work with Ruby Gems, so picked this random
Ruby port to see how porting Gems works.

I did not had a chance to test anything yet.

-- 
best regards
q#



Re: UPDATE: devel/ruby-bundler to 1.3.5

2013-04-28 Thread Jeremy Evans
On Sun, Apr 28, 2013 at 3:01 AM, Mikolaj Kucharski
miko...@kucharski.namewrote:

 I've tried and no joy -- regress is not happy, and regress is doing here
 some really invasive stuff, which will probably fail with systrace
 (untested). I'm attaching the output from make test. Also, below patch
 contains my debugging patches, which should probably be removed, but I
 kept them, so someone more experienced with Ruby and Ruby ports could
 have a look what should be done with that part of code, if anything
 actually needs to be done.


Most of the remaining failures are due to other programs not being
found because of their extension (ruby/rackup/rake).  You could
probably fix this by adding them to post-extract.

The regress tests should probably be commented out by default,
since they are downloading gems.

Are you upgrading bundler because a dependency requires a newer
version, or just to get the most current version?  In either case, have
you verified the existing dependencies are OK with the newer version?

Jeremy