[Bug 818458] Review Request: rubygem-ruby-debug19 - Command line interface (CLI) for ruby-debug-base

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



https://bugzilla.redhat.com/show_bug.cgi?id=818458

Toby Ovod-Everett <toby@xxxxxxxxxxxxxxxx> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |toby@xxxxxxxxxxxxxxxx

--- Comment #2 from Toby Ovod-Everett <toby@xxxxxxxxxxxxxxxx> ---
This is just a comment from one user to encourage someone to take on the review
of this package (and it's Depends On, 818457).  I noticed that Mamoru TASAKA
and Bohuslav "Slavek" Kabrda were very successful in getting
rubygem-linecache19 through QA and released (thanks!), but rubygem-ruby-debug19
and rubygem-ruby-debug-base19 seem to be stalled.

My goal as an end user is to have ruby itself and a minimal set of additional
packages (ruby-devel, rubygem-bundler, rubygem-rake, and their dependencies)
installed and then to manage all the other gems (including rails, rack, etc.)
using bundler on a per-user basis.

This seems to be working reasonably well, but I can't use bundler to install
ruby-debug19 because the various gems involved all appear to require a full
copy of the source tree (or at least files that aren't included in ruby-devel,
like vm_core.h).  I'd rather not have to keep installing the source tree on a
per-user basis and customizing bundler in order to get it to find the source
tree (plus worrying about keeping it up-to-date every time there's a backport
of a patch).

As a result, I'd like to add ruby-debug19 into my list of minimal additional
packages, but unfortunately Mamoru TASAKA's work seems to be hung up waiting
for someone else to do a package review.

As it is, I'll just live without the debugger, but it would be really cool if
someone (perhaps even Bohuslav "Slavek" Kabrda) were to do the package review
on the two debug19 packages.  I just learned that the package review process
exists from reading the history on
https://bugzilla.redhat.com/show_bug.cgi?id=818454, which should explain why I
am not qualified or permitted to do one!

Thanks so much for the work you are all doing to make Ruby easier to use on
Fedora - it is really appreciated.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
package-review mailing list
package-review@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/package-review



[Index of Archives]     [Fedora Legacy]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [KDE Users]     [Fedora Tools]