On Nov 9, 2007, at 16:23 , Trans wrote: > On Nov 9, 2007 5:31 PM, Eric Hodel <[EMAIL PROTECTED]> wrote: >> On Nov 5, 2007, at 07:02 , Luis Lavena wrote: >>>> I wish we had unified packages, though, rather then having to >>>> create >>>> separate packages for each platform. >>> >>> The problem will that will be how identify extensions compiled for >>> windows, linux or darwin, all in the same package. >>> >>> Kernel#require is not clever as rubygems require version to find the >>> matching -mswin32 or -darwin or -bsd version of the specific >>> extension. >> >> At RubyConf, we (RubyGems & ruby-core members) decided moving away >> from modifying Kernel#require was a good thing. >> >> Besides, there are plenty of tools to completely automate every step >> of releasing a gem. If you're doing it right, releasing a platform >> gem is as easy as `rake release`. > > Yes. I've reconsidered my position. I think a platform gem is a rather > special case. For instance a Windows binary, b/c Windows often lacks > the needed compile tools. But on most other systems it seems > unccessary. Is that a fair assessment?
I think so. Most other systems have compilers by default, or a compiler can easily be added to them. -- Poor workers blame their tools. Good workers build better tools. The best workers get their tools to do the work for them. -- Syndicate Wars _______________________________________________ Rubygems-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/rubygems-developers
