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

Bug#1009727: O: ruby-curses -- curses binding for Ruby



Hi Andrej,

Andrej Shadura wrote:
> > Shall I close this bug already again as you still seem to care about
> > ruby-curses in contrary to what you stated back in 2020?
> 
> No, I still don’t intend to continue maintaining it 🙂

*g*

> I originally packaged it as a dependency of a Ruby implementation of
> git-crecord which I wanted to package. However, I quickly became
> unsatisfied with it and instead ported the Python code of hg-crecord
> to Git, so ruby-curses became useless to me.

I see, thanks for that background information.

> If your package uses ruby-curses, it would be great if you could
> maintain this package in the Ruby team.

I was already thinking about doing an NMU or QA upload, but I
currently don't intend to adopt ruby-curses for various reasons:

* I've nearly no experience with Ruby and no experience with ruby
  library packaging or the according workflow at all.

* I already maintain too many packages. :-/

* The package in question (irqtop) is just a bycatch of the source
  package's main package I'm interested in: iptables-netflow-dkms.

  It sidekick irqtop is mostly a performance analysis and debug tool
  for that kernel module despite it has more general use cases, too.

  And I don't want ruby dependencies in a kernel module package for
  high performance traffic statistics. :-)

* The future of the irqtop package is a bit unclear since util-linux
  upstream introduced a C written command of the same name recently,
  too. See https://bugs.debian.org/1009668 for that discussion.

Anyway, thanks to your upload the most annoying issue with irqtop (the
ruby-written one) is now gone. Thanks again! :-)

		Regards, Axel
-- 
 ,''`.  |  Axel Beckert <abe@debian.org>, https://people.debian.org/~abe/
: :' :  |  Debian Developer, ftp.ch.debian.org Admin
`. `'   |  4096R: 2517 B724 C5F6 CA99 5329  6E61 2FF9 CD59 6126 16B5
  `-    |  1024D: F067 EA27 26B9 C3FC 1486  202E C09E 1D89 9593 0EDE


Reply to: