How do you plan to handle rapid updates? Yes, sometimes Pry can go
months without a proper build but sometimes it will only be mere days
and it's a rapidly evolving tool by developers for developers (I also
think this should be held off for at least a couple of months since a
new version is probably coming out soon) and unless you plan to also
package it's plugins you leave things wide open for a select few
plugins which are always built for the latest Pry including those who
might be hooking into newer hooks which Debians version will not have
if it's slow to update or it will be really out of sync with the wiki.
If you guys put this in right now I believe you guys will be way out
of sync here soon too since there are a few planned major refactors to
On Wed, Feb 22, 2012 at 5:43 PM, Youhei SASAKI <uwabami@...> wrote:
> At Mon, 20 Feb 2012 11:41:20 +0100,
> Paul van Tilburg <paulvt@...> wrote:
>> On Mon, Feb 20, 2012 at 07:10:09PM +0900, Youhei SASAKI wrote:
>> > Package: wnpp
>> > Owner: Youhei SASAKI <uwabami@...>
>> > Severity: wishlist
>> > * Package name : ruby-pry
>> As this is an application, I would suspect it to be called 'pry'.
> Very thanks for your suggestion. I'll change package name and team
> repositoy. These package are ready to be uploaded. Could you please
> sponsor them?
> pry: Powerfull irb alternative and runtime developer console
> ruby-slop: Simple DSL for gathering options and parsing the command lineOpts
> ruby-method-source: Retrieve the sourcecode for a method as a Ruby string
> The pry depends ruby-slop and ruby-method-source.