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 4B90917C77C8 for ; Tue, 26 Jun 2012 22:09:45 +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 80FA3EA6BC9 for ; Tue, 26 Jun 2012 22:07:18 +0900 (JST) Received: from localhost (localhost.nagaokaut.ac.jp [127.0.0.1]) by funfun.nagaokaut.ac.jp (Postfix) with ESMTP id 8F8608FC29 for ; Tue, 26 Jun 2012 22:07:19 +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 7CM4yia2orIa for ; Tue, 26 Jun 2012 22:07:19 +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 6E7F58FC1B for ; Tue, 26 Jun 2012 22:07:19 +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 D69CF952429 for ; Tue, 26 Jun 2012 22:07:15 +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 1BDA23C229400; Tue, 26 Jun 2012 22:07:13 +0900 (JST) Received: from fluorine.ruby-lang.org (www.rubyist.net [210.251.121.216]) by carbon.ruby-lang.org (Postfix) with ESMTP id 5AEA83C229408 for ; Tue, 26 Jun 2012 22:07:05 +0900 (JST) Received: from ruby-lang.org (localhost [127.0.0.1]) by fluorine.ruby-lang.org (Postfix) with ESMTP id 48EDC3ED5A for ; Tue, 26 Jun 2012 22:07:05 +0900 (JST) Delivered-To: ruby-core@ruby-lang.org Date: Tue, 26 Jun 2012 22:07:05 +0900 Posted: Tue, 26 Jun 2012 22:07:05 +0900 From: "mrkn (Kenta Murata)" Reply-To: ruby-core@ruby-lang.org Subject: [ruby-core:45886] [ruby-trunk - Feature #6590][Third Party's Issue] Dealing with bigdecimal, etc gems in JRuby To: ruby-core@ruby-lang.org Message-Id: References: X-ML-Name: ruby-core X-Mail-Count: 45886 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= X-Mailer: Redmine X-Redmine-Issue-Author: headius X-Redmine-Issue-Assignee: mrkn X-Auto-Response-Suppress: OOF X-Redmine-Issue-Id: 6590 X-Redmine-Mailinglistintegration-Message-Ids: 16140 X-Redmine-Project: ruby-trunk Auto-Submitted: auto-generated X-Redmine-Site: Ruby Issue Tracking System X-Redmine-Host: bugs.ruby-lang.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 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: Issue #6590 has been updated by mrkn (Kenta Murata). Status changed from Assigned to Third Party's Issue ---------------------------------------- Feature #6590: Dealing with bigdecimal, etc gems in JRuby https://bugs.ruby-lang.org/issues/6590#change-27481 Author: headius (Charles Nutter) Status: Third Party's Issue Priority: Normal Assignee: mrkn (Kenta Murata) Category: Target version: Hello! http://jira.codehaus.org/browse/JRUBY-6704 We have a need to make the "bigdecimal" gem work for JRuby, so that distros (like Red Hat, mentioned in the above bug) and users can have the same gemspec for JRuby with updated bigdecimal gem references. I'm not sure the best way to proceed. The bigdecimal source and gemspec all come from MRI source, and are not versioned separately. That means we can't simply share a repository for the JRuby bits. We could maintain a forked version in our forked "jruby/ruby" repository, but that wouldn't be part of the bigdecimal release cycle then. So I'm looking to you for guidance. The BigDecimal lib is here in JRuby: https://github.com/jruby/jruby/tree/master/src/org/jruby/ext/bigdecimal It might be simplest if for now there's a dummy "bigdecimal" gem pushed for JRuby that does not contain anything, since we would have other complications if we tried to remove BigDecimal from JRuby proper (it is referenced elsewhere int eh code, etc). Thoughts? - Charlie -- http://bugs.ruby-lang.org/