Summary: | media-sound/podcatcher-3.1.6 version bump | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | chkno |
Component: | New packages | Assignee: | Gentoo Sound Team <sound> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jstein, ruby |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
chkno
2012-07-08 07:38:06 UTC
I've committed the bump, but this probably needs someone familiar with ruby to implement the ruby-ng.eclass functionality. (In reply to comment #1) > I've committed the bump, but this probably needs someone familiar with ruby > to implement the ruby-ng.eclass functionality. I had a quick look and this is only a binary, so the ruby-ng eclass can't help. I think the ebuild looks fine from as-is and will default to the currently eselected ruby. If anything the previous version was broken as it should have depended on dev-lang/ruby:1.8. Currently it pulls in both ruby:1.8 and ruby:1.9 (when no ruby previously installed). Surely that's more than necessary. (In reply to comment #3) > Currently it pulls in both ruby:1.8 and ruby:1.9 (when no ruby previously > installed). Surely that's more than necessary. I guess this only happens with USE=bittorrent? In that case dev-ruby/rubytorrent is pulled in, and that is only marked for ruby18. Thus ruby 1.9 gets pulled in for podcatcher and 1.8 for rubytorrent. In this situation I would suggest to limit the ruby dependency of podcatcher to ruby:1.8 to reflect its dependencies. rubytorrent has seen not a release since 2005 and it has no test suite, so I won't mark it ready for ruby19 unless there are some positive test reports from users. * media-sound/podcatcher Available versions: (~)3.1.6 Homepage: http://podcatcher.rubyforge.org/ Description: Podcast client for the command-line written in Ruby |