I hate to follow up my own message but 

pack.rb line 156 (my older version of shoes) has this line of ruby
  dmg.grow(10)

That seems like an arbitrary number that some folks have reported. I
don't know what dmg.grow() does, but a hacker might up that to 30 or 40
and see what happens. Or one could read the docs for binject. Where that
pack.rb is on your system and which copy of shoes you are using if you
have multiples... 

Just something to look at.
--Cecil


On Fri, 2009-05-22 at 21:00 -0600, Cecil Coupe wrote:
> It might be easier to debug and fix the problem than implement a
> workaround, IMHO. It looks like most of the action starts in
> lib/shoes/pack.rb - I don't have an OS X box anymore so I can't be very
> helpful. Might be an easy fix if you can find all the parts.
> 
> 
> 
> On Fri, 2009-05-22 at 21:24 -0500, Roy Wright wrote:
> > Maybe as a work around, implement a download and install ffmpeg as
> > needed instead of including the binary in the package?  Similar to how a
> > shoes app can download and install shoes...
> > 
> > HTH,
> > Roy
> > 
> > Noah Thorp wrote:
> > > Thanks for the encouragement. I have plans to post the open source
> > > transcoder (ffmpeg wrapper) once it had reaches a certain level of alpha
> > > maturity. It's a very simple but useful app. I could post it to github
> > > early if it would help troubleshooting. But, it seems like it may be an
> > > issue simply with including large files in an OS X package.
> > > 
> > > Thanks,
> > > Noah
> > > 
> > > On May 22, 2009, at 5:31 PM, e deleflie wrote:
> > > 
> > >> Hi Noah,
> > >>
> > >> I dont think you are falling outside of the use case it was intended
> > >> for ... I think its just a bug.
> > >>
> > >> I dont have a work-around for you .... (maybe someone else does) ...
> > >> but if we shout loud enough .... _why might hear our plea to have a
> > >> look at this bug.
> > >>
> > >> So it looks like large binaries (5 to 10MB and up?) included in a
> > >> folder and packaged up, for OSX, cause the packager to crash.
> > >>
> > >> Etienne
> > >>
> > 
> 

Reply via email to