From: "mame (Yusuke Endoh)" <mame@tsg.ne.jp>
To: ruby-core@ruby-lang.org
Subject: [ruby-core:49923] [ruby-trunk - Feature #6590] Dealing with bigdecimal, etc gems in JRuby
Date: Sat, 24 Nov 2012 09:10:39 +0900 [thread overview]
Message-ID: <redmine.journal-33682.20121124091038@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-6590.20120614132114@ruby-lang.org
Issue #6590 has been updated by mame (Yusuke Endoh).
Target version set to next minor
----------------------------------------
Feature #6590: Dealing with bigdecimal, etc gems in JRuby
https://bugs.ruby-lang.org/issues/6590#change-33682
Author: headius (Charles Nutter)
Status: Assigned
Priority: Normal
Assignee: nahi (Hiroshi Nakamura)
Category:
Target version: next minor
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/
next prev parent reply other threads:[~2012-11-24 0:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-6590.20120614132114@ruby-lang.org>
2012-06-14 4:21 ` [ruby-core:45643] [ruby-trunk - Feature #6590][Assigned] Dealing with bigdecimal, etc gems in JRuby naruse (Yui NARUSE)
2012-06-26 13:06 ` [ruby-core:45885] [ruby-trunk - Feature #6590] " mrkn (Kenta Murata)
2012-06-26 13:07 ` [ruby-core:45886] [ruby-trunk - Feature #6590][Third Party's Issue] " mrkn (Kenta Murata)
2012-06-26 15:59 ` [ruby-core:45889] [ruby-trunk - Feature #6590][Open] " marcandre (Marc-Andre Lafortune)
2012-06-27 0:13 ` [ruby-core:45903] [ruby-trunk - Feature #6590] " hasari (Hiro Asari)
2012-06-29 5:47 ` [ruby-core:45948] " vo.x (Vit Ondruch)
2012-07-01 7:22 ` [ruby-core:46049] " mrkn (Kenta Murata)
2012-07-02 14:51 ` [ruby-core:46110] " Aaron Patterson
2012-07-03 2:58 ` [ruby-core:46125] " KOSAKI Motohiro
2012-07-03 9:30 ` [ruby-core:46136] " Alex Young
2012-07-03 4:35 ` [ruby-core:46128] " vo.x (Vit Ondruch)
2012-07-03 8:01 ` [ruby-core:46132] " KOSAKI Motohiro
2012-07-03 9:02 ` [ruby-core:46135] " vo.x (Vit Ondruch)
2012-07-03 23:12 ` [ruby-core:46153] " headius (Charles Nutter)
2012-07-14 9:36 ` [ruby-core:46460] [ruby-trunk - Feature #6590][Assigned] " mame (Yusuke Endoh)
2012-10-19 6:03 ` [ruby-core:48106] [ruby-trunk - Feature #6590] " elninorian (menuju sukses sukses)
2012-11-24 0:10 ` mame (Yusuke Endoh) [this message]
2019-05-15 12:53 ` [ruby-core:92660] [Ruby trunk Feature#6590] " hsbt
2019-05-15 20:33 ` [ruby-core:92666] " eregontp
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-33682.20121124091038@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).