It's great to see this discussion. As a developer, I just want to
‘require "bananas"’ and see it work.
I come from a Rails background, so I know that gem dependencies can
create all sorts of problems. As Macruby becomes more popular, these
problems are going to become more apparent as the diversity
Btw, I don't think a Gemfile adds anything for a bundled production
app besides that our shim would have to support the DSL. I think the
dev should just use ‘require "bananas"’ in her code and it should just
work. I.e. the Gemfile is I think only needed in development and at
release time.
On Sat,
Yes, what we need is a tool that resolves dependencies at release time
and bundle these in the app. The app also have a shim that makes sure
that if any of the bundled dependencies call Kernel#gem it doesn't
break. I.e. on the clients machine rubygems should not actually be
loaded to ensure as fast
On 2011-01-29, at 02:11 , Matt Aimonetti wrote:
>
> IMHO adding Bundler as a dependency would be a huge mistake. First, Bundler
> code is overly complicated and tries to do way too much.
(You forgot to mention slow.)
I think I agree here. I just like the Gemfile format. Don't think we need to
IMHO adding Bundler as a dependency would be a huge mistake. First, Bundler
code is overly complicated and tries to do way too much. Trying to resolve the
dependency tree is not something you should do in prod or on a client machine.
This belongs to the dev environment.
We could potentially look
On 2011-01-28, at 21:36 , Laurent Sansonetti wrote:
>
> I would rather avoid any dependency. I agree that keeping track of the gems
> you need in a single place is a good idea, though.
>
> Maybe we should refactor the Xcode templates to do so, eventually.
I'd classify Xcode as a dependency. Sim
Hi Caio,
On Jan 28, 2011, at 2:39 PM, Caio Chassot wrote:
> On 2011-01-28, at 20:30 , Laurent Sansonetti wrote:
>>
>> As I suggested on IRC yesterday, I think we should add a --gem argument to
>> macruby_deploy, which would make sure the given gems and their dependencies
>> are unpacked inside
On 2011-01-28, at 20:30 , Laurent Sansonetti wrote:
>
> As I suggested on IRC yesterday, I think we should add a --gem argument to
> macruby_deploy, which would make sure the given gems and their dependencies
> are unpacked inside the application bundle.
It could be great if this involved a bit
Hi Martin,
I think we now get the "how to embed gems in a MacRuby Xcode project?" question
every week. I think it's time that we provide a way to automate that and
properly document it on the website.
As I suggested on IRC yesterday, I think we should add a --gem argument to
macruby_deploy, wh
Well, I've just realised that get the fileutils message was in fact a
sign of some success, as the UUID gem does indeed require it.
I'll play around a little more with gem loading - I've got to get it
right for other projects. I was doing what you suggested but without
apparent success.
wrt CFUUID
On Fri, Jan 28, 2011 at 12:41 PM, Martin Hawkins
wrote:
> In rb_main.rb
>
> $:.unshift File.join(File.dirname(__FILE__), 'Vendor/uuid-2.3.1/lib')
> $:.unshift File.join(File.dirname(__FILE__), 'Vendor/macaddr-1.0.0/
> lib')
>
> require 'macaddr'
> require 'uuid'
>
> However, when I try to requir
Yes, they will. This is a work in progress, though.
Laurent
On Dec 28, 2008, at 10:35 AM, Brad Hutchins wrote:
What about Ruby Gems? If they are 1.9 compatible. Will they work
on MacRuby?
___
MacRuby-devel mailing list
[email protected]
12 matches
Mail list logo
