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 the application bundle.
>
> It could be great if this involved a bit of magic, so you only specify the
> gems you need in a single place.
>
> Maybe it's overkill, but we could rely on Bundler. I'm a Bundler hater turned
> devotee. It really helps keep a tight grip on a project's gem dependencies,
> locking versions and all. With the added benefit to pull gems from custom
> paths and git repos.
>
> I suppose such support could be built on top of a simpler --gem argument in a
> rake task, though.
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. Another
possibility would be to scan the application's source code and auto-detect the
list of gems, but I prefer to avoid that.
Laurent
_______________________________________________
MacRuby-devel mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
