From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: poffice@blade.nagaokaut.ac.jp Delivered-To: poffice@blade.nagaokaut.ac.jp Received: from kankan.nagaokaut.ac.jp (kankan.nagaokaut.ac.jp [133.44.2.24]) by blade.nagaokaut.ac.jp (Postfix) with ESMTP id 75A3A17C8DE1 for ; Tue, 3 Jul 2012 17:03:59 +0900 (JST) Received: from funfun.nagaokaut.ac.jp (smtp.nagaokaut.ac.jp [133.44.2.201]) by kankan.nagaokaut.ac.jp (Postfix) with ESMTP id B8324EA6BFF for ; Tue, 3 Jul 2012 17:01:21 +0900 (JST) Received: from localhost (localhost.nagaokaut.ac.jp [127.0.0.1]) by funfun.nagaokaut.ac.jp (Postfix) with ESMTP id 7CAC88FC2A for ; Tue, 3 Jul 2012 17:01:22 +0900 (JST) X-Virus-Scanned: amavisd-new at funfun.nagaokaut.ac.jp Received: from funfun.nagaokaut.ac.jp ([127.0.0.1]) by localhost (funfun.nagaokaut.ac.jp [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TGvPtaXE0CaP for ; Tue, 3 Jul 2012 17:01:22 +0900 (JST) Received: from voscc.nagaokaut.ac.jp (voscc.nagaokaut.ac.jp [133.44.1.100]) by funfun.nagaokaut.ac.jp (Postfix) with ESMTP id 5BE428FC1B for ; Tue, 3 Jul 2012 17:01:22 +0900 (JST) Received: from carbon.ruby-lang.org (carbon.ruby-lang.org [221.186.184.68]) by voscc.nagaokaut.ac.jp (Postfix) with ESMTP id A41FE952593 for ; Tue, 3 Jul 2012 17:01:19 +0900 (JST) Received: from beryllium.ruby-lang.org (beryllium.ruby-lang.org [127.0.0.1]) by carbon.ruby-lang.org (Postfix) with ESMTP id E3BE63C21E7B1; Tue, 3 Jul 2012 17:01:17 +0900 (JST) Received: from mail-pb0-f50.google.com (mail-pb0-f50.google.com [209.85.160.50]) by carbon.ruby-lang.org (Postfix) with ESMTP id 1AC683C2294BD for ; Tue, 3 Jul 2012 17:01:16 +0900 (JST) Received: by pbbrr4 with SMTP id rr4so10553029pbb.37 for ; Tue, 03 Jul 2012 01:01:16 -0700 (PDT) Received: by 10.68.211.41 with SMTP id mz9mr5008889pbc.12.1341302476192; Tue, 03 Jul 2012 01:01:16 -0700 (PDT) Received: by 10.68.48.69 with HTTP; Tue, 3 Jul 2012 01:00:56 -0700 (PDT) Delivered-To: ruby-core@ruby-lang.org Date: Tue, 3 Jul 2012 17:01:17 +0900 Posted: Tue, 3 Jul 2012 04:00:56 -0400 From: KOSAKI Motohiro Reply-To: ruby-core@ruby-lang.org Subject: [ruby-core:46132] Re: [ruby-trunk - Feature #6590] Dealing with bigdecimal, etc gems in JRuby To: ruby-core@ruby-lang.org Message-Id: In-Reply-To: References: X-ML-Name: ruby-core X-Mail-Count: 46132 X-MLServer: fml [fml 4.0.3 release (20011202/4.0.3)]; post only (only members can post) X-ML-Info: If you have a question, send e-mail with the body "help" (without quotes) to the address ruby-core-ctl@ruby-lang.org; help= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=evglD60bamAQd219Fd7vlu7FDhzell7KMe7Uq2xLVS0=; b=Mwfyob6WOlUjvs1I40Y/JbiPmz5V8KfU+aOqZw2PbBgbm7sJbV70YOrFOLFkcsIkxO 1WT9/empj2yAsSdu5F4zmwN+zHSLnRpTNt7gVT40/Ip2hQPGZ7Kk4mu583/ZXlRR4H0y Jup5SbwBTyMJU7AtxP0eGxtW0G6JaxoCEx2GMFQlcvS09qPfwDUoUsJcquETDYQF4t8X YV6unJ88hvu++dRXBwDYgStv7UiDRYw0sGUwsueuD9XX3x6Nj7PVZfu/H/mMP/q0Atvh UX377x2TMC/P6+2n+2hhhy3dAshL1vh1OMNnjnN478oy4KeVbMK3ysIpegYajYIpZ7T3 ca+Q== Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Precedence: bulk List-Id: ruby-core.ruby-lang.org List-Software: fml [fml 4.0.3 release (20011202/4.0.3)] List-Post: List-Owner: List-Help: List-Unsubscribe: On Tue, Jul 3, 2012 at 12:35 AM, vo.x (Vit Ondruch) wrote: > > Issue #6590 has been updated by vo.x (Vit Ondruch). > > > kosaki (Motohiro KOSAKI) wrote: >> Actually, this is not bigdecimal issue. It is gem discovery issue. MRI >> support two extension types, >> C and Ruby. JRuby also support two extension types, Java and Ruby. gem >> loader should realized >> the fact and prefer to look up Java implementation when used from >> JRuby. I think. > > Actually that is exactly what RubyGems do and what Aaron is proposing. Ta= ke nokogiri [1] for example. If you are using MRI, then the nokogiri gem is= taken. If it happens you are windows user, then RubyGems downloads nokogir= i-x86-mingw32 and if you are JRuby user, then the nokogiri-java version is = prefered. They are all just nokogiris, so RubyGems takes the gems from one = location. So the MRI gem will be uploaded by mkrn and the JRuby version by = headius. It should be just somehow synchronized when new gem version is rel= eased. I disagree. JRuby bigdecimal is not equal with mrkn bigdecimal. It is a forked gem. They were maintained different maintainer and different repository. We can't synchronized them anytime. So, No. Please drop f*cking insane idea. It doesn work at all.