pkgsrc-Users archive

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

ruby-libnotify and gem (Re: CVS commit: pkgsrc)




To: pkgsrc-users%NetBSD.org@localhost

Subject: ruby-libnotify and gem (Re: CVS commit: pkgsrc)

From: Izumi Tsutsui <tsutsui%ceres.dti.ne.jp@localhost>

Date: Sat, 30 Jan 2016 10:15:03 +0900


joerg@ wrote on pkgsrc-changes@:

> On Sun, Jan 24, 2016 at 05:03:24AM +0000, Izumi Tsutsui wrote:
> > Log Message:
> > Switch ruby-gnome2 packages to using gem.
> 
> Can you take a look at sysutils/ruby-libinotify please? It can no longer
> find the ruby-gnom2-glib headers.

Hmm, you meant sysutils/ruby-libnotify?

I would like to suggest to remove this ruby-libnotify because:

- no "Required by" pkgsrc users
 http://pkgsrc.se/sysutils/ruby-libnotify

- upstream is inactive since 2012 (i.e. no updates after Ruby 2.0 release)
 https://github.com/vargolo/ruby-libnotify/commits/master 

- it has hardcoded Config::CONFIG["sitearchdir"] path so
  won't support gem'fied glib even with the native gem
 https://github.com/vargolo/ruby-libnotify/blob/8ba5861daf9c46e2b9893bea50030520ef355954/ext/extconf.rb#L46

- it looks there is a more active alternative for users who actually need
  libnotify functions
 https://rubygems.org/search?query=libnotify

Or should I still put kludge to current one to pacify builds?

---
Izumi Tsutsui


Follow-Ups:

Re: ruby-libnotify and gem (Re: CVS commit: pkgsrc)
From: Joerg Sonnenberger




Prev by Date: Re: firefox 44.0 build/install fails on NetBSD-amd64

Next by Date: bootstrap failure with gcc53 for 2015Q4 on linux, aix

Previous by Thread: net/gnome-online-accounts: patch and buildlink

Next by Thread: Re: ruby-libnotify and gem (Re: CVS commit: pkgsrc)

Indexes:

reverse Date

reverse Thread

Old Index



Home | Main Index | Thread Index | Old Index