remove x-generate-plist and friends
- use RF macro and remove SUBDIR where possible
- remove some uneeded GEM_NAME=${DISTNAME}
(this c/should be handled better in bsd.*.mk)
other deltas specific to individual ports:
audio/rubygem-mp3info - unbreak, fix packaging, bump PORTREVISION
devel/rubygem-rapt - adopt
devel/rubygem-rspec - remove BUILD_DEPENDS=RUN_DEPENDS -- neither set
devel/rubygem-ruby2ruby - add #' for vim highlight
graphics/rubygem-extifr - drop PORTREVISION=0
graphics/rubygem-gd2 - add #' for vim highlight
www/rubygem-rubyfulsoup - swap GEM_NAME / DISTNAME for constistency
Sponsored by: RideCharge Inc.
Tested on: RideCharge's Tinderbox
Reviewed by: stas
- Implement new knobs for gems and rake (these are included in
ruby 1.9 distribution already). Also move gem bits from
ruby-gems/Makefile.common to bsd.ruby.mk[1]. Now to depend
on gems or rake you should define USE_RUBYGEMS/USE_RAKE
accordingly. Also RAKE_BIN variable is provided for
pointing to the right rake executable.
- Rewrite RUBY_SCHEBANG in awk to eliminate build dependency
on ruby.
Discussed with: Jonathan Weiss <jw@innerewut.de> [1] (gems maintainer)
Tested by: ports@
It's designed to be a useful quick-and-dirty parser for screen-scraping,
along the same lines as its parent:
1. Rubyful Soup won't choke if you give it bad markup. It yields a parse tree
that makes approximately as much sense as your original document.
This is usually good enough to collect the data you need and then run away.
2. Rubyful Soup provides a few simple methods and Ruby-like idioms for
navigating and searching a parse tree: a toolkit for dissecting a document
and extracting what you need. You don't have to create a custom parser for
each application. It's more flexible and easier to learn than XPath.
WWW: http://www.crummy.com/software/BeautifulSoup/
