I think these ports can be purged (FWIW, the only one I use is Bacon: a
great little test framework).
But honestly I just get my ruby software via `gem install` and have been
doing so for many years. It works great. Once in awhile there is a gem
that gives me a problem, for example nokogiri, but tweaking a few make
flags usually fixes it right up. I've found this the best and easiest
way to stay patched and get anything I need when I need it.
With that said, Jeremy, I greatly appreciate your effort in keeping the
ruby language and gem system up to date. Thank you.
P.S. jcs@, I dearly miss the garbage podcast. When I see a new show was
downloaded, I get excited. Thank you too man.
Clint
Jeremy Evans wrote on 11/03/17 09:16:
I would like to remove the pure ruby gem ports listed below. I reviewed
all of our pure ruby gem ports and used the following criteria:
1) No significant updates in the last few years
2) Gem version we are using was released over 7 years ago
3) No other port depends on it
Here's a list of the ports and the year the gem version we are using was
released:
databases/ruby-validatable # 2008
devel/ruby-bacon # 2008
devel/ruby-clio # 2008
devel/ruby-color-tools # 2005
devel/ruby-ffi-inliner # 2010
devel/ruby-gem_plugin # 2007
devel/ruby-mspec # 2010
devel/ruby-needle # 2005
devel/ruby-stringex # 2009
net/ruby-nmap-parser # 2009
net/ruby-xmpp4r # 2008
security/ruby-ezcrypto # 2009
security/ruby-yadis # 2007
textproc/ruby-ascii85 # 2009
textproc/ruby-classifier # 2010
textproc/ruby-htmlentities # 2007
textproc/ruby-markaby # 2006
textproc/ruby-pdf-reader # 2009
textproc/ruby-rtex # 2009
textproc/ruby-templater # 2009
www/ruby-thin_http # 2008
OKs?
Thanks,
Jeremy
