| Summary: | Retire rubygem-ParseTree | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Bohuslav "Slavek" Kabrda <bkabrda> |
| Component: | rubygem-ParseTree | Assignee: | Mo Morsi <mmorsi> |
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | rawhide | CC: | mmorsi |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-02-14 17:09:23 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Bohuslav "Slavek" Kabrda
2012-02-08 08:37:57 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. 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. |