of the files, instead of all lines. Additionally, loosen the regexp
slightly so that it handles more cases automatically. This makes
ruby.port.mk's behavior similar to python.port.mk.
OK sthen@
for consistency with the gem/extconf ports.
Update non-gem/extconf ports that relied on the previous
default of ruby 1.8 to explicitly specify it.
OK ajacoutot@
Refactor the conflicting FLAVOR code to be less verbose,
thanks to sthen@. Additional indentation fixes from sthen@.
Modify the jruby code to work with jruby 1.7.
Deal with newer gems containing checksum files by deleting
the checksums.
the use of the ruby18 FLAVOR to explicitly build a version for ruby 1.8.
To handle updates, add a @pkgpath marker with the unflavored PKGPATH
to all ruby18 FLAVOR gem/extconf PLISTs.
Remove format-executable CONFIGURE_STYLE, since only one port uses it.
Instead, allow the port Makefile to set GEM_FLAGS, and have ruby.port.mk
append to that if it already exists.
is not set, but only for gem, extconf, and setup based ports. Other
ports could be using the lang/ruby module and still have a standard
make-based regression test suite.
rspec 1 using rspec and rspec 2 using rspec2. Additionally, add
support for ruby and testrb, calling the appropriate binary for the
ruby implementation.
Start checking sanity of MODRUBY_REGRESS entry, using a fatal error
if it is defined and doesn't contain a recognized word.
Instead of RAKE_REGRESS_TARGET and RSPEC_REGRESS_TARGET, just use
MODRUBY_REGRESS_TARGET for all cases. On ruby 1.9, modifying the
environment to always look in the current directory for libraries
(the ruby 1.8 behavior), since many ports depend on that for regress.
Allow ports to set their own regress environment and current directory
using MODRUBY_REGRESS_ENV and MODRUBY_REGRESS_DIR.
which should allow building on arches without enough memory to
generate the ri files. Also, set PKG_ARCH=* for the ri_docs
subpackage, so that such arches can still use the documentation,
idea from sthen@. Original idea for PSUEDO_FLAVOR from phessler@.
OK sthen@
that no longer create .require_paths files. No RUN_DEPENDS
are being added as older ruby versions can use gems without
.require_paths files (we never had a ruby 1.9.1 package).
This is being done to avoid errors by porters who are creating/updating
gem ports without installing new ruby versions.
a few new features. A few of our patches were accepted upstream.
Add an -ri_docs multipackage to hold the ri documentation files. These
aren't used very often, slow down installation significantly, and bloat
the package.
This also fixes the conflict marker for the -tk multipackage.
