use a subpackage instead. This was split previously because gnome-keyring
required linking pthread causing file-descriptor I/O issues with the main
binary. ok stsp@
which can be triggered by clients. Please update your servers (it doesn't
matter whether you use svnserve or mod_dav_svn, you need to update).
A corresponding update for -stable ports will follow.
ok jasper sthen dcoppa
Previously, we were using ruby->=1.8,<=1.9, instead of
ruby->=1.8,<1.9. While this wouldn't cause an issue, since
our ruby-1.9.2 package isn't included in ruby->=1.8,<=1.9,
it's still wrong and should be fixed. This also fixes the
following minor issues:
Switch from using FLAVOR to MODRUBY_FLAVOR for *_DEPENDS.
Currently we don't have a ruby port that uses FLAVORs that
would differ from MODRUBY_FLAVOR, but it's possible we will
in the future.
Switch from BASE_PKGPATH to BUILD_PKGPATH in a few cases in
REGRESS_DEPENDS. This probably is not strictly necessary, but
BUILD_PKGPATH is used in more cases, so it is good for
consistency.
Switch to new style *_DEPENDS, with the version specification
at the end. The remaining cases where this is not done is
because a specific version is used.
Some FULLPKGNAME added to REGRESS_DEPENDS, to make sure that if
the old version is installed when you run a regress test, it
will install the new version first.
Some conversion of spaces to tabs for consistency.
OK landry@
into MODRUBY_WANTLIB and using CONFIGURE_STYLE = ruby gem ext. Use the
lang/ruby module for all dependent ports, setting
MODRUBY_{BUILD,RUN}DEP=No if necessary.
ok landry, phessler, sthen
isn't already installed. The dependency on autoconf used to be
implicit until CONFIGURE_STYLE was switched from autoconf to gnu
during the 1.6.11 update.
From Daniel Dickman.
Also change the configure style to 'gnu' instead of 'autoconf'
to avoid running autoconf twice (autoconf is run by the autogen.sh
script in the pre-configure target). landy@ says this fixes the
build on hppa for some reason.
ok aja, landry (for the configure-style bit some time ago)
