I was not thinking about a dependency framework, just a clean way to mark gems are MacRuby only. RubyGems already has something builtin:
spec.platform = Gem::Platform::Win32 I'm just not sure what to use for MacRuby and how to deal with this issue cleanly. - Matt On Mon, Mar 9, 2009 at 2:58 PM, Eloy Duran <[email protected]> wrote: > Hey Matt, > > I think a gem is fine. You can always choose to vendor it when you deploy. > (Something which Rucola for instance does.) > > Taking on the responsibility of a dependency framework is a bit too far > away from where the current focus of MacRuby should lie imho. > > Eloy > > > On 9 mrt 2009, at 22:13, Matt Aimonetti wrote: > > Hey Guys, >> >> I worked on a JSON lib for MacRuby which uses a dynlib. I'm thinking >> about making it in a gem but it would only be compatible with MacRuby. I >> feel like we should discuss this as a group and try to come up with a >> standard way of dealing with this challenge. >> >> - Matt >> _______________________________________________ >> MacRuby-devel mailing list >> [email protected] >> http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >> > > _______________________________________________ > MacRuby-devel mailing list > [email protected] > http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel >
_______________________________________________ MacRuby-devel mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macruby-devel
