Bug 788440 - Retire rubygem-ParseTree
Summary: Retire rubygem-ParseTree
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: rubygem-ParseTree
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mo Morsi
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-08 08:37 UTC by Bohuslav "Slavek" Kabrda
Modified: 2012-02-14 17:09 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-14 17:09:23 UTC
Type: ---

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Bohuslav "Slavek" Kabrda 2012-02-08 08:37:57 UTC 
Hi,
according to [1], rubygem-ParseTree doesn't work with Ruby 1.9.3, so it should be retired in Fedora 17. (It's also not needed by any other packages).

[1] https://github.com/seattlerb/parsetree/issues/1
Comment 1 Mo Morsi 2012-02-08 18:49:11 UTC 
It should still work with JRuby correct? Actually brings up a use case that we hadn't thought about, how to ship a gem that works w/ one interpreter but not another. Thoughts?

Still seems like the project is receiving some attention upstream so not sure if retiring the package is the best course of action.
Comment 2 Mo Morsi 2012-02-14 17:09:23 UTC 
On further thought, since there are no existing dependencies on this package, I have retired for the time being.

rubygem-sexp_processor seems to be a fork that is more maintained.
Note You need to log in before you can comment on or make changes to this bug.