decibel.kde.org does not exist anymore, there is nothing in KDE that uses it
and the whole project has been dead upstream for many years.
Removing it also allows us to later get rid of the old net-im/tapioca-qt and
net-im/telepathy-qt ports.
- Use USE_GNOME= ltverhack to correct the library version number
to what the author intended. This effectively rolls the version
number backwards, but should prevent future unneccesary version
bumps.
- Support staging
- Use options helpers
- Use new LIB_DEPENDS syntax
- Bump PORTREVISION on dependent ports
2013-10-10 audio/ruby-xmms: Does not work with Ruby 1.9
2013-10-10 databases/ruby-interbase: Does not work with Ruby 1.9
2013-10-10 databases/ruby-bdb1: Does not work with Ruby 1.9
2013-10-10 devel/ruby-fam: Does not work with Ruby 1.9
2013-10-10 devel/ruby-rcov: Does not work with Ruby 1.9
2013-10-10 devel/ruby-rudl: Does not work with Ruby 1.9
2013-10-10 devel/ruby-gemfinder: Does not work with Ruby 1.9
2013-10-10 devel/ruby-sysvipc: Does not work with Ruby 1.9
2013-10-10 devel/rubygem-sdl: Does not work with Ruby 1.9
2013-10-10 devel/rubygem-ncurses: Does not work with Ruby 1.9
2013-10-10 devel/rubygem-parsetree: Does not work with Ruby 1.9
2013-10-10 devel/ruby-sexp: Does not work with Ruby 1.9
2013-10-10 devel/rubygem-getopt-declare: Does not work with Ruby 1.9
2013-10-10 devel/ruby-slang: Does not work with Ruby 1.9
2013-10-10 japanese/ruby-slang: Does not work with Ruby 1.9
2013-10-10 devel/ruby-gettext: Does not work with Ruby 1.9
2013-10-10 devel/ruby-jttui: Does not work with Ruby 1.9
2013-10-10 devel/ruby-mmap: Does not work with Ruby 1.9
2013-10-10 devel/ruby-racc: Does not work with Ruby 1.9
2013-10-10 devel/rubygem-rparsec: Does not work with Ruby 1.9
2013-10-10 devel/rubygem-zoom: Does not work with Ruby 1.9
2013-10-10 games/ruby-exmars: Does not work with Ruby 1.9
2013-10-10 graphics/ruby-pgplot: Does not work with Ruby 1.9
2013-10-10 graphics/ruby-opengl: Does not work with Ruby 1.9
2013-10-10 graphics/rubygem-turing: Does not work with Ruby 1.9
2013-10-10 japanese/ruby-chasen: Does not work with Ruby 1.9
2013-10-10 japanese/ruby-gyokuro: Does not work with Ruby 1.9
2013-10-10 japanese/ruby-rdic: Does not work with Ruby 1.9
2013-10-10 lang/ruby-mode.el: Does not work with Ruby 1.9
2013-10-10 misc/rubygem-ohcount: Does not work with Ruby 1.9
2013-10-10 net-im/rubygem-xmpp4r: Does not work with Ruby 1.9
2013-10-10 security/ruby-acl: Does not work with Ruby 1.9
2013-10-10 textproc/ruby-xslt: Does not work with Ruby 1.9
2013-10-10 textproc/ruby-erbscan: Does not work with Ruby 1.9
2013-10-10 textproc/ruby-mwdom: Does not work with Ruby 1.9
2013-10-10 textproc/ruby-xmlscan-old: Does not work with Ruby 1.9
2013-10-10 textproc/rubygem-formosa: Does not work with Ruby 1.9
2013-10-10 textproc/rubygem-htmltools: Does not work with Ruby 1.9
2013-10-10 www/ruby-cruisecontrolrb: Does not work with Ruby 1.9
2013-10-10 www/rubygem-rubyfulsoup: Does not work with Ruby 1.9
2013-10-10 x11/ruby-gtktrayicon: Does not work with Ruby 1.9
It appears that the -v option (verbose) is handled slightly differently
on DragonFly. FreeBSD appears to be intolerant of where it appears in
the command line while the DragonFly version of "install" insists that
it appear in the early group of options.
In any case, these three ports may be the only ones in the entire ports
collection to use -v switch with ${INSTALL_DATA}, so for the sake of
compatibility and consistency, it is being removed from these
unmaintained ports which also local patches to be removed from DPorts.
In addition to the header inclusion, the linking stage failed on modern
binutils because libX11 was used without being explicitly listed. The
LDFLAGS from the Makefile were getting overwritten by the CMake makefile,
so that had to be patch to allow the LDFLAGS to be appended.
Approved by: portmgr (bapt, implicit)
