[DRE-maint] Bug#712954: Status on ITP ruby-launchy ?

[Youhei SASAKI]

Hi,

At Fri, 07 Mar 2014 14:23:08 +0100,
Dominique Dumont <dod at debian.org> wrote:
>
> On Tuesday 25 February 2014 11:55:25 Cédric Boutillier wrote:
> > The last point to do was renaming /usr/bin/launchy to something else
> > (launchy-rb?) because there was already a binary with that name in the
> > archive. If I remember well, the rest was more than OK.
>
> Anyway, I was interested in runy-launchy because newer jekyll depends on it.
>
> But here's how jekyll uses launchy:
>
>  $ grep -Ri Launchy Rakefile lib script/ site/ test/
>  Rakefile:    require "launchy"
>  Rakefile:      Launchy.open("http://localhost:4000")
>  site/docs/history.md:- Update launchy dependency to `~> 2.3` ([#1608]
> ({{{site.repository }}/issues/1608))
>
> That's all: launchy is used only to launch a web browser.

Yes.

> In the case of jekyll, I'd recommend to patch jekyll to use xdg-open directly
> instead of using launchy.

I don't want/recommend. 

Because other software depends Jekyll may potentially depend Launchy. We
provides rubygems-integration, thus, we should provides completely
dependecies. Or we create/provide new abstraction layer in order to
resolve dependencies and use xdg-open directly. 

Again, we should provides ruby-launchy package.

Best Wishes,
Youhei

---
Youhei SASAKI <uwabami at gfd-dennou.org>
              <uwabami at debian.or.jp>
GPG fingerprint:
  4096/RSA: 66A4 EA70 4FE2 4055 8D6A C2E6 9394 F354 891D 7E07