cpet/openbsd-ports
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
eb23d649c1
openbsd-ports/lang/ruby/ruby.port.mk

416 lines
13 KiB
Makefile
Raw Normal View History

Add MODRUBY_HANDLE_FLAVORS variable which can be set to No to not have the lang/ruby module add FLAVORS automatically for gem and extconf ports, or to Yes to enable the FLAVORS for non-gem and non-extconf ports. Add a MODRUBY_BIN_TESTRB variable containing the appropriate testrb command for use in regress tests. OK landry@
2011-03-24 17:26:59 -04:00
# $OpenBSD: ruby.port.mk,v 1.44 2011/03/24 21:26:59 jeremy Exp $
Add ruby module, ok espie@
2002-03-17 17:29:02 -05:00
# ruby module
add MODRUBY_BUILD_DEPENDS to stay consistent with other modules
2009-08-11 05:20:23 -04:00
CATEGORIES+= lang/ruby
Add MODRUBY_HANDLE_FLAVORS variable which can be set to No to not have the lang/ruby module add FLAVORS automatically for gem and extconf ports, or to Yes to enable the FLAVORS for non-gem and non-extconf ports. Add a MODRUBY_BIN_TESTRB variable containing the appropriate testrb command for use in regress tests. OK landry@
2011-03-24 17:26:59 -04:00
# Whether the ruby module should automatically add FLAVORs.
# If left blank, does so only for gem and extconf ports.
.if ${CONFIGURE_STYLE:L:Mgem} || ${CONFIGURE_STYLE:L:Mextconf}
MODRUBY_HANDLE_FLAVORS ?= Yes
.else
MODRUBY_HANDLE_FLAVORS ?= No
.endif
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
# This allows you to build ruby 1.8, ruby 1.9, and jruby packages using
# the same port directory for gem and extconf based ports. It does this
# by adding FLAVORS automatically, unless FLAVORS are already defined
# or the port defines MODRUBY_REV to tie the port to a specific ruby
# version. For example, JDBC gem ports want to set MODRUBY_REV=jruby,
# since they don't work on ruby 1.8 or ruby 1.9.
.if !defined(MODRUBY_REV)
Add MODRUBY_HANDLE_FLAVORS variable which can be set to No to not have the lang/ruby module add FLAVORS automatically for gem and extconf ports, or to Yes to enable the FLAVORS for non-gem and non-extconf ports. Add a MODRUBY_BIN_TESTRB variable containing the appropriate testrb command for use in regress tests. OK landry@
2011-03-24 17:26:59 -04:00
. if ${MODRUBY_HANDLE_FLAVORS:L:Myes}
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
. if !defined(FLAVORS)
Allow building of gem ext and extconf based ports with jruby, since jruby 1.6.0 now supports them. Require at least jruby 1.6.0 when building/running a gem ext or extconf port. Since jruby no longer bundles RSpec, simplify the MODRUBY_RSPEC_DEPENDS handling. OK landry@
2011-03-18 19:04:22 -04:00
FLAVORS?= ruby19 rbx jruby
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
. endif
# Instead of adding flavors to the end of the package name, we use
# different package stems for ruby 1.8, ruby 1.9, and jruby packages.
# ruby 1.8 uses the historical ruby-* package stem, ruby 1.9 uses
# ruby19-* and jruby uses jruby-*. In most cases, PKGNAME in the port
# should be set to the same as DISTNAME, and this will insert the
# correct package prefix.
Fix various minor issues in ruby.port.mk: * No longer remove ruby-* from PKGNAME when building FULLPKGNAME for the gem and extconf ports * Correctly remove ruby18 FLAVOR * Use extract/build/install cookies * Fix installing of certain gems as root without systrace, by working around a bug in devel/ruby-gems * Remove MODRUBY_REV from SUBST_VARS OK landry@
2010-11-16 13:30:38 -05:00
FULLPKGNAME?= ${MODRUBY_PKG_PREFIX}-${PKGNAME}
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
# If the port can work on both ruby 1.9 and another version of ruby,
# and gem installs binaries for it, the binaries on ruby 1.9 are installed
# with a 19 suffix. GEM_BIN_SUFFIX should be added after such a filename
# in the PLIST so that the gem will correctly package on all supported
Add GEM_MAN_SUFFIX so that gem ports with man pages can avoid conflicts. Also, base MODRUBY_PKG_PREFIX on MODRUBY_FLAVOR to avoid some duplication. OK landry@
2011-03-14 16:39:20 -04:00
# versions of ruby. Because the rbx, jruby, and default FLAVORs all use
# same binary names but in different directories, GEM_MAN_SUFFIX is
# used for the man pages to avoid conflicts since all man files go
# in the same directory.
SUBST_VARS+= GEM_BIN_SUFFIX GEM_MAN_SUFFIX
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
FLAVOR?=
Deal with the rubinius directory changes, and tie rbx FLAVORs to the currently supported minor version of rubinius. No longer allow a ruby18 FLAVOR to be used to specify ruby 1.8. Now, only the empty flavor should be used. OK landry@
2011-01-05 23:15:46 -05:00
# Without a FLAVOR, assume the use of ruby 1.8.
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
. if empty(FLAVOR)
MODRUBY_REV= 1.8
# Check for conflicting FLAVORs and set MODRUBY_REV appropriately based
# on the FLAVOR.
. elif ${FLAVOR:L:Mruby19}
Deal with the rubinius directory changes, and tie rbx FLAVORs to the currently supported minor version of rubinius. No longer allow a ruby18 FLAVOR to be used to specify ruby 1.8. Now, only the empty flavor should be used. OK landry@
2011-01-05 23:15:46 -05:00
. if ${FLAVOR:L:Mjruby} || ${FLAVOR:L:Mrbx}
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
ERRORS+= "Fatal: Conflicting flavors used: ${FLAVOR}"
. endif
MODRUBY_REV= 1.9
. elif ${FLAVOR:L:Mjruby}
Deal with the rubinius directory changes, and tie rbx FLAVORs to the currently supported minor version of rubinius. No longer allow a ruby18 FLAVOR to be used to specify ruby 1.8. Now, only the empty flavor should be used. OK landry@
2011-01-05 23:15:46 -05:00
. if ${FLAVOR:L:Mruby19} || ${FLAVOR:L:Mrbx}
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
ERRORS+= "Fatal: Conflicting flavors used: ${FLAVOR}"
. endif
MODRUBY_REV= jruby
Allow building of rubinius versions of the ruby gem and extconf ports using the rbx FLAVOR and the rbx- package prefix. OK landry@, sthen@
2010-11-19 12:54:37 -05:00
. elif ${FLAVOR:L:Mrbx}
Deal with the rubinius directory changes, and tie rbx FLAVORs to the currently supported minor version of rubinius. No longer allow a ruby18 FLAVOR to be used to specify ruby 1.8. Now, only the empty flavor should be used. OK landry@
2011-01-05 23:15:46 -05:00
. if ${FLAVOR:L:Mruby19} || ${FLAVOR:L:Mjruby}
Allow building of rubinius versions of the ruby gem and extconf ports using the rbx FLAVOR and the rbx- package prefix. OK landry@, sthen@
2010-11-19 12:54:37 -05:00
ERRORS+= "Fatal: Conflicting flavors used: ${FLAVOR}"
. endif
MODRUBY_REV= rbx
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
. endif
. endif
.endif
# Other non-gem and non-extconf based ruby ports should default to
# using ruby 1.8. Ports that require a different ruby version such
# set MODRUBY_REV in their makefile with either 1.9 or jruby to
# build on ruby 1.9 or jruby respectively.
MODRUBY_REV?= 1.8
Add GEM_MAN_SUFFIX so that gem ports with man pages can avoid conflicts. Also, base MODRUBY_PKG_PREFIX on MODRUBY_FLAVOR to avoid some duplication. OK landry@
2011-03-14 16:39:20 -04:00
# Have the man pages for the rbx and jruby versions of a gem file
# use an -rbx or -jruby suffix to avoid conflicts with the
# default ruby 1.8 man page.
GEM_MAN_SUFFIX = -${MODRUBY_FLAVOR}
# Use the FLAVOR as the prefix for the package, to avoid conflicts.
# Each of the FLAVORs defined in ruby.port.mk should be independent
# from the others if possible.
MODRUBY_PKG_PREFIX = ${MODRUBY_FLAVOR}
GEM_BIN_SUFFIX =
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
.if ${MODRUBY_REV} == 1.8
Split the lang/ruby port into separate ports for ruby 1.8 and ruby 1.9, similar to how the lang/python ports are handled. ruby 1.8 now installs as ruby18 and ruby 1.9 installs as ruby19. The included MESSAGE files for both ports let you know the symlinks to set up if you want to make that version the default system ruby. Split port originally started by bernd@, many changes since by me, help and support from jcs@, landry@, jasper@, and sthen@. This causes a large amount of fallout in dependent ruby ports, which will be committed shortly. OK jcs@, landry@, jasper@, sthen@
2010-09-23 17:58:50 -04:00
MODRUBY_LIBREV= 1.8
MODRUBY_BINREV= 18
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
MODRUBY_PKG_PREFIX= ruby
MODRUBY_FLAVOR =
Add GEM_MAN_SUFFIX so that gem ports with man pages can avoid conflicts. Also, base MODRUBY_PKG_PREFIX on MODRUBY_FLAVOR to avoid some duplication. OK landry@
2011-03-14 16:39:20 -04:00
GEM_MAN_SUFFIX =
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
.elif ${MODRUBY_REV} == 1.9
MODRUBY_LIBREV= 1.9.1
MODRUBY_BINREV= 19
MODRUBY_FLAVOR = ruby19
GEM_BIN_SUFFIX= 19
Add GEM_MAN_SUFFIX so that gem ports with man pages can avoid conflicts. Also, base MODRUBY_PKG_PREFIX on MODRUBY_FLAVOR to avoid some duplication. OK landry@
2011-03-14 16:39:20 -04:00
# Have the ruby 1.9 manpage match the binary name.
GEM_MAN_SUFFIX = ${GEM_BIN_SUFFIX}
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
.elif ${MODRUBY_REV} == jruby
MODRUBY_LIBREV= 1.8
Rename REV and SUB variables to MODRUBY_REV and MODRUBY_ARCH. Keep the old ones around until the dependent ports have been synced. ok msf@, 'I like it' sturm@
2006-07-14 11:41:21 -04:00
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
# Set these during development of ruby.port.mk to make sure
# nothing is broken. However, turn them off before committing,
# since they result in bad error messages when, for example, an
# invalid flavor is used.
#.poison MODRUBY_BINREV
#.poison MODRUBY_WANTLIB
MODRUBY_FLAVOR = jruby
Allow building of rubinius versions of the ruby gem and extconf ports using the rbx FLAVOR and the rbx- package prefix. OK landry@, sthen@
2010-11-19 12:54:37 -05:00
.elif ${MODRUBY_REV} == rbx
MODRUBY_LIBREV = 1.8
#.poison MODRUBY_BINREV
#.poison MODRUBY_WANTLIB
MODRUBY_FLAVOR = rbx
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
.endif
MODRUBY_RAKE_DEPENDS =
Allow building of gem ext and extconf based ports with jruby, since jruby 1.6.0 now supports them. Require at least jruby 1.6.0 when building/running a gem ext or extconf port. Since jruby no longer bundles RSpec, simplify the MODRUBY_RSPEC_DEPENDS handling. OK landry@
2011-03-18 19:04:22 -04:00
MODRUBY_RSPEC_DEPENDS = devel/ruby-rspec,${MODRUBY_FLAVOR}
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
# Set the path for the ruby interpreter and the rake and rspec
# commands used by MODRUBY_REGRESS and manually in some port
# targets.
.if ${MODRUBY_REV} == jruby
RUBY= ${LOCALBASE}/jruby/bin/jruby
RAKE= ${RUBY} -S rake
RSPEC= ${RUBY} -S spec
Add MODRUBY_HANDLE_FLAVORS variable which can be set to No to not have the lang/ruby module add FLAVORS automatically for gem and extconf ports, or to Yes to enable the FLAVORS for non-gem and non-extconf ports. Add a MODRUBY_BIN_TESTRB variable containing the appropriate testrb command for use in regress tests. OK landry@
2011-03-24 17:26:59 -04:00
MODRUBY_BIN_TESTRB = ${RUBY} -S testrb
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
# Without this, JRuby often fails with a memory error.
MAKE_ENV+= JAVA_MEM='-Xms256m -Xmx256m'
Allow building of rubinius versions of the ruby gem and extconf ports using the rbx FLAVOR and the rbx- package prefix. OK landry@, sthen@
2010-11-19 12:54:37 -05:00
.elif ${MODRUBY_REV} == rbx
RUBY= ${LOCALBASE}/bin/rbx
RAKE= ${RUBY} -S rake
RSPEC= ${RUBY} -S spec
Add MODRUBY_HANDLE_FLAVORS variable which can be set to No to not have the lang/ruby module add FLAVORS automatically for gem and extconf ports, or to Yes to enable the FLAVORS for non-gem and non-extconf ports. Add a MODRUBY_BIN_TESTRB variable containing the appropriate testrb command for use in regress tests. OK landry@
2011-03-24 17:26:59 -04:00
MODRUBY_BIN_TESTRB = ${RUBY} -S testrb
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
.else
Split the lang/ruby port into separate ports for ruby 1.8 and ruby 1.9, similar to how the lang/python ports are handled. ruby 1.8 now installs as ruby18 and ruby 1.9 installs as ruby19. The included MESSAGE files for both ports let you know the symlinks to set up if you want to make that version the default system ruby. Split port originally started by bernd@, many changes since by me, help and support from jcs@, landry@, jasper@, and sthen@. This causes a large amount of fallout in dependent ruby ports, which will be committed shortly. OK jcs@, landry@, jasper@, sthen@
2010-09-23 17:58:50 -04:00
RUBY= ${LOCALBASE}/bin/ruby${MODRUBY_BINREV}
RAKE= ${LOCALBASE}/bin/rake${MODRUBY_BINREV}
Add MODRUBY_HANDLE_FLAVORS variable which can be set to No to not have the lang/ruby module add FLAVORS automatically for gem and extconf ports, or to Yes to enable the FLAVORS for non-gem and non-extconf ports. Add a MODRUBY_BIN_TESTRB variable containing the appropriate testrb command for use in regress tests. OK landry@
2011-03-24 17:26:59 -04:00
MODRUBY_BIN_TESTRB = ${LOCALBASE}/bin/testrb${MODRUBY_BINREV}
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
. if ${MODRUBY_REV} == 1.8
new depends
2010-11-17 03:05:12 -05:00
MODRUBY_RAKE_DEPENDS = devel/ruby-rake
Add support for several popular ruby regression test suites accessible via the MODRUBY_REGRESS variable. discussed with and ok bernd@
2009-08-11 10:30:15 -04:00
RSPEC= ${LOCALBASE}/bin/spec
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
. else
RSPEC= ${LOCALBASE}/bin/spec${MODRUBY_BINREV}
. endif
.endif
Add support for several popular ruby regression test suites accessible via the MODRUBY_REGRESS variable. discussed with and ok bernd@
2009-08-11 10:30:15 -04:00
MODRUBY_REGRESS?=
add CONFIGURE_STYLE "ruby setup" and related targets move LIB_DEPENDS to relevant ports, no PKGNAME bump needed this is in preparation of a soon to come ruby-gems port with msf's consent
2006-06-11 14:57:11 -04:00
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
.if ${MODRUBY_REV} == jruby
Allow building of gem ext and extconf based ports with jruby, since jruby 1.6.0 now supports them. Require at least jruby 1.6.0 when building/running a gem ext or extconf port. Since jruby no longer bundles RSpec, simplify the MODRUBY_RSPEC_DEPENDS handling. OK landry@
2011-03-18 19:04:22 -04:00
. if ${CONFIGURE_STYLE:L:Mext} || ${CONFIGURE_STYLE:L:Mextconf}
# Only jruby 1.6.0+ can build C extensions
MODRUBY_RUN_DEPENDS= lang/jruby>=1.6.0
. else
new depends
2010-11-17 03:05:12 -05:00
MODRUBY_RUN_DEPENDS= lang/jruby
Allow building of gem ext and extconf based ports with jruby, since jruby 1.6.0 now supports them. Require at least jruby 1.6.0 when building/running a gem ext or extconf port. Since jruby no longer bundles RSpec, simplify the MODRUBY_RSPEC_DEPENDS handling. OK landry@
2011-03-18 19:04:22 -04:00
. endif
Allow building of rubinius versions of the ruby gem and extconf ports using the rbx FLAVOR and the rbx- package prefix. OK landry@, sthen@
2010-11-19 12:54:37 -05:00
.elif ${MODRUBY_REV} == rbx
MODRUBY_RUN_DEPENDS= lang/rubinius
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
.else
Split library spec from MODRUBY_LIB_DEPENDS into MODRUBY_WANTLIB. Also, if CONFIGURE_STYLE includes ext or extconf, update WANTLIB and LIB_DEPENDS, and set SHARED_ONLY=Yes. That configure style is only used for ruby C extensions, which need those settings. This cleans up a lot of ruby C extension ports, which will be committed shortly. ok landry, phessler, sthen
2010-10-26 17:14:24 -04:00
MODRUBY_WANTLIB= ruby${MODRUBY_BINREV}
Remove MODRUBY_PKGSPEC, rely on the PKGSPEC entries specified in lang/ruby/1.*/Makefile. Also, add the ability to pass CONFIGURE_ARGS to gem install. These get passed to the extconf.rb scripts that create the Makefiles for C extensions, and may make it easier to port gems with C extensions without resorting to patching. OK landry@
2010-11-24 16:30:36 -05:00
MODRUBY_RUN_DEPENDS= lang/ruby/${MODRUBY_REV}
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
.endif
Split library spec from MODRUBY_LIB_DEPENDS into MODRUBY_WANTLIB. Also, if CONFIGURE_STYLE includes ext or extconf, update WANTLIB and LIB_DEPENDS, and set SHARED_ONLY=Yes. That configure style is only used for ruby C extensions, which need those settings. This cleans up a lot of ruby C extension ports, which will be committed shortly. ok landry, phessler, sthen
2010-10-26 17:14:24 -04:00
MODRUBY_LIB_DEPENDS= ${MODRUBY_RUN_DEPENDS}
add MODRUBY_BUILD_DEPENDS to stay consistent with other modules
2009-08-11 05:20:23 -04:00
MODRUBY_BUILD_DEPENDS= ${MODRUBY_RUN_DEPENDS}
Add lang/ruby to CATEGORIES. All ports using this module will be bumped. tested in a bulk build and ok bernd@
2008-06-14 19:40:35 -04:00
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
.if ${MODRUBY_REV} == 1.8
Remove MODRUBY_PKGSPEC, rely on the PKGSPEC entries specified in lang/ruby/1.*/Makefile. Also, add the ability to pass CONFIGURE_ARGS to gem install. These get passed to the extconf.rb scripts that create the Makefiles for C extensions, and may make it easier to port gems with C extensions without resorting to patching. OK landry@
2010-11-24 16:30:36 -05:00
MODRUBY_ICONV_DEPENDS= ruby-iconv->=1.8,<1.9:lang/ruby/${MODRUBY_REV},-iconv
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
.else
MODRUBY_ICONV_DEPENDS= ${MODRUBY_RUN_DEPENDS}
.endif
Split the lang/ruby port into separate ports for ruby 1.8 and ruby 1.9, similar to how the lang/python ports are handled. ruby 1.8 now installs as ruby18 and ruby 1.9 installs as ruby19. The included MESSAGE files for both ports let you know the symlinks to set up if you want to make that version the default system ruby. Split port originally started by bernd@, many changes since by me, help and support from jcs@, landry@, jasper@, and sthen@. This causes a large amount of fallout in dependent ruby ports, which will be committed shortly. OK jcs@, landry@, jasper@, sthen@
2010-09-23 17:58:50 -04:00
add comments
2002-12-09 16:04:08 -05:00
# location of ruby libraries
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
.if ${MODRUBY_REV} == jruby
MODRUBY_LIBDIR= ${LOCALBASE}/jruby/lib/ruby
Allow building of rubinius versions of the ruby gem and extconf ports using the rbx FLAVOR and the rbx- package prefix. OK landry@, sthen@
2010-11-19 12:54:37 -05:00
.elif ${MODRUBY_REV} == rbx
Deal with the rubinius directory changes, and tie rbx FLAVORs to the currently supported minor version of rubinius. No longer allow a ruby18 FLAVOR to be used to specify ruby 1.8. Now, only the empty flavor should be used. OK landry@
2011-01-05 23:15:46 -05:00
MODRUBY_LIBDIR= ${LOCALBASE}/lib/rubinius
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
.else
Added doc and example directories
2002-12-09 15:26:36 -05:00
MODRUBY_LIBDIR= ${LOCALBASE}/lib/ruby
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
.endif
add comments
2002-12-09 16:04:08 -05:00
# common directories for ruby extensions
# used to create docs and examples install path
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
MODRUBY_RELDOCDIR= share/doc/${MODRUBY_PKG_PREFIX}
MODRUBY_RELEXAMPLEDIR= share/examples/${MODRUBY_PKG_PREFIX}
MODRUBY_DOCDIR= ${PREFIX}/${MODRUBY_RELDOCDIR}
MODRUBY_EXAMPLEDIR= ${PREFIX}/${MODRUBY_RELEXAMPLEDIR}
SUBST_VARS += ^MODRUBY_RELDOCDIR ^MODRUBY_RELEXAMPLEDIR
.if ${MODRUBY_REV} == jruby
MODRUBY_ARCH= ${MACHINE_ARCH:S/amd64/x86_64/}-java
.else
Rename REV and SUB variables to MODRUBY_REV and MODRUBY_ARCH. Keep the old ones around until the dependent ports have been synced. ok msf@, 'I like it' sturm@
2006-07-14 11:41:21 -04:00
MODRUBY_ARCH= ${MACHINE_ARCH:S/amd64/x86_64/}-openbsd${OSREV}
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
.endif
Add ruby module, ok espie@
2002-03-17 17:29:02 -05:00
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
# Assume that we want to automatically add ruby to BUILD_DEPENDS
# and RUN_DEPENDS unless the port specifically requests not to.
Add MODRUBY_RUNDEP and MODRUBY_BUILDDEP, modelled on python.port.mk. ok jeremy@
2010-10-24 05:16:13 -04:00
MODRUBY_BUILDDEP?= Yes
MODRUBY_RUNDEP?= Yes
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
.if ${NO_BUILD:L} == no && ${MODRUBY_BUILDDEP:L} == yes
Add support for several popular ruby regression test suites accessible via the MODRUBY_REGRESS variable. discussed with and ok bernd@
2009-08-11 10:30:15 -04:00
BUILD_DEPENDS+= ${MODRUBY_BUILD_DEPENDS}
Add MODRUBY_RUNDEP and MODRUBY_BUILDDEP, modelled on python.port.mk. ok jeremy@
2010-10-24 05:16:13 -04:00
.endif
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
.if ${MODRUBY_RUNDEP:L} == yes
Add support for several popular ruby regression test suites accessible via the MODRUBY_REGRESS variable. discussed with and ok bernd@
2009-08-11 10:30:15 -04:00
RUN_DEPENDS+= ${MODRUBY_RUN_DEPENDS}
Add MODRUBY_RUNDEP and MODRUBY_BUILDDEP, modelled on python.port.mk. ok jeremy@
2010-10-24 05:16:13 -04:00
.endif
Add support for several popular ruby regression test suites accessible via the MODRUBY_REGRESS variable. discussed with and ok bernd@
2009-08-11 10:30:15 -04:00
.if ${MODRUBY_REGRESS:L:Mrake}
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
REGRESS_DEPENDS+= ${MODRUBY_RAKE_DEPENDS}
Add support for several popular ruby regression test suites accessible via the MODRUBY_REGRESS variable. discussed with and ok bernd@
2009-08-11 10:30:15 -04:00
.endif
.if ${MODRUBY_REGRESS:L:Mrspec}
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
REGRESS_DEPENDS+= ${MODRUBY_RSPEC_DEPENDS}
Add support for several popular ruby regression test suites accessible via the MODRUBY_REGRESS variable. discussed with and ok bernd@
2009-08-11 10:30:15 -04:00
.endif
Add MODRUBY_RUBY_ADJ and MODRUBY_ADJ_FILES. MODRUBY_RUBY_ADJ is a perl command that accepts filename arguments and modifies the common /usr/bin/env ruby shebang to ${RUBY}. MODRUBY_ADJ_FILES is a short cut that allows you to set filename patterns and have MODRUBY_RUBY_ADJ called on all files in ${WRKSRC} that match that pattern. It adds a pre-configure action to do so, if a pre-configure action is not already defined. If a pre-configure action is already defined, you can call the replacement command with ${MODRUBY_ADJ_REPLACE}. ok sthen, landry
2010-10-07 13:48:53 -04:00
MODRUBY_RUBY_ADJ= perl -pi -e 's,/usr/bin/env ruby,${RUBY},'
MODRUBY_ADJ_FILES?=
.if !empty(MODRUBY_ADJ_FILES)
MODRUBY_ADJ_REPLACE= for pat in ${MODRUBY_ADJ_FILES:QL}; do \
quote pattern and only work on files (-type f) in MODRUBY_ADJ_REPLACE. From Mikolaj Kucharski on ports@, ok sthen@ jeremy@
2010-11-10 04:00:10 -05:00
find ${WRKSRC} -type f -name "$$pat" -print0 | \
Add MODRUBY_RUBY_ADJ and MODRUBY_ADJ_FILES. MODRUBY_RUBY_ADJ is a perl command that accepts filename arguments and modifies the common /usr/bin/env ruby shebang to ${RUBY}. MODRUBY_ADJ_FILES is a short cut that allows you to set filename patterns and have MODRUBY_RUBY_ADJ called on all files in ${WRKSRC} that match that pattern. It adds a pre-configure action to do so, if a pre-configure action is not already defined. If a pre-configure action is already defined, you can call the replacement command with ${MODRUBY_ADJ_REPLACE}. ok sthen, landry
2010-10-07 13:48:53 -04:00
xargs -0r ${MODRUBY_RUBY_ADJ} ; \
done
. if !target(pre-configure)
pre-configure:
${MODRUBY_ADJ_REPLACE}
. endif
.endif
Fix various minor issues in ruby.port.mk: * No longer remove ruby-* from PKGNAME when building FULLPKGNAME for the gem and extconf ports * Correctly remove ruby18 FLAVOR * Use extract/build/install cookies * Fix installing of certain gems as root without systrace, by working around a bug in devel/ruby-gems * Remove MODRUBY_REV from SUBST_VARS OK landry@
2010-11-16 13:30:38 -05:00
MODRUBY_EXTRACT_COOKIE = ${WRKDIR}/.modruby_extract_done
MODRUBY_BUILD_COOKIE = ${WRKBUILD}/.modruby_build_done
MODRUBY_INSTALL_COOKIE = ${WRKINST}/.modruby_install_done
Split library spec from MODRUBY_LIB_DEPENDS into MODRUBY_WANTLIB. Also, if CONFIGURE_STYLE includes ext or extconf, update WANTLIB and LIB_DEPENDS, and set SHARED_ONLY=Yes. That configure style is only used for ruby C extensions, which need those settings. This cleans up a lot of ruby C extension ports, which will be committed shortly. ok landry, phessler, sthen
2010-10-26 17:14:24 -04:00
.if ${CONFIGURE_STYLE:L:Mext} || ${CONFIGURE_STYLE:L:Mextconf}
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
# Ruby C exensions are specific to an arch and are loaded as
# shared libraries (not compiled into ruby), so set SHARED_ONLY
# and make sure PKG_ARCH=* is not set.
. if defined(PKG_ARCH) && ${PKG_ARCH} == *
ERRORS+= "Fatal: Should not have PKG_ARCH=* when compiling extensions"
. endif
Split library spec from MODRUBY_LIB_DEPENDS into MODRUBY_WANTLIB. Also, if CONFIGURE_STYLE includes ext or extconf, update WANTLIB and LIB_DEPENDS, and set SHARED_ONLY=Yes. That configure style is only used for ruby C extensions, which need those settings. This cleans up a lot of ruby C extension ports, which will be committed shortly. ok landry, phessler, sthen
2010-10-26 17:14:24 -04:00
SHARED_ONLY= Yes
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
# All ruby C extensions are dependent on libc and ruby's library, and almost
# all are also dependment on libm, so include c, m, and ruby's library by
# default, but let the port maintainer opt out of libm by setting
# MODRUBY_WANTLIB_m=No.
Split library spec from MODRUBY_LIB_DEPENDS into MODRUBY_WANTLIB. Also, if CONFIGURE_STYLE includes ext or extconf, update WANTLIB and LIB_DEPENDS, and set SHARED_ONLY=Yes. That configure style is only used for ruby C extensions, which need those settings. This cleans up a lot of ruby C extension ports, which will be committed shortly. ok landry, phessler, sthen
2010-10-26 17:14:24 -04:00
WANTLIB+= c ${MODRUBY_WANTLIB}
MODRUBY_WANTLIB_m?= Yes
. if ${MODRUBY_WANTLIB_m:L:Myes}
WANTLIB+= m
. endif
LIB_DEPENDS+= ${MODRUBY_LIB_DEPENDS}
Deal with the rubinius directory changes, and tie rbx FLAVORs to the currently supported minor version of rubinius. No longer allow a ruby18 FLAVOR to be used to specify ruby 1.8. Now, only the empty flavor should be used. OK landry@
2011-01-05 23:15:46 -05:00
. if ${MODRUBY_REV} == rbx
# Tighten dependency on rubinius when a C extension is used. Rubinius
# does not maintain binary compatibility across minor versions.
MODRUBY_RUN_DEPENDS = lang/rubinius>=1.2,<1.3
. endif
Split library spec from MODRUBY_LIB_DEPENDS into MODRUBY_WANTLIB. Also, if CONFIGURE_STYLE includes ext or extconf, update WANTLIB and LIB_DEPENDS, and set SHARED_ONLY=Yes. That configure style is only used for ruby C extensions, which need those settings. This cleans up a lot of ruby C extension ports, which will be committed shortly. ok landry, phessler, sthen
2010-10-26 17:14:24 -04:00
.endif
remove the default CONFIGURE_STYLE and CONFIGURE_SCRIPT into the new 'ruby extconf' CONFIGURE_STYLE this allows us to pull ruby.port.mk into fun things like subversion ok bernd@
2006-11-27 04:36:14 -05:00
.if ${CONFIGURE_STYLE:L:Mextconf}
CONFIGURE_STYLE= simple
Split the lang/ruby port into separate ports for ruby 1.8 and ruby 1.9, similar to how the lang/python ports are handled. ruby 1.8 now installs as ruby18 and ruby 1.9 installs as ruby19. The included MESSAGE files for both ports let you know the symlinks to set up if you want to make that version the default system ruby. Split port originally started by bernd@, many changes since by me, help and support from jcs@, landry@, jasper@, and sthen@. This causes a large amount of fallout in dependent ruby ports, which will be committed shortly. OK jcs@, landry@, jasper@, sthen@
2010-09-23 17:58:50 -04:00
CONFIGURE_SCRIPT= ${RUBY} extconf.rb
remove the default CONFIGURE_STYLE and CONFIGURE_SCRIPT into the new 'ruby extconf' CONFIGURE_STYLE this allows us to pull ruby.port.mk into fun things like subversion ok bernd@
2006-11-27 04:36:14 -05:00
.elif ${CONFIGURE_STYLE:L:Mgem}
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
# All gems should be in the same directory on rubygems.org.
Remove MASTER_SITES from most ruby gem ports, specify it in ruby.port.mk All ruby .gem files are now hosted on rubygems.org in the same directory. If the ruby gem CONFIGURE_STYLE is used, make the default MASTER_SITES that directory. There are still a few uses of MASTER_SITE_RUBYFORGE in the tree, for some ports that aren't gems, or where the .gem file isn't hosted on rubygems.org, or where the hashes don't match. Most of these will be dealt with in the near future. OK landry@
2010-09-28 16:12:16 -04:00
MASTER_SITES?= ${MASTER_SITE_RUBYGEMS}
support for CONFIGURE_STYLE "ruby gem" with msf's consent
2006-06-11 15:56:31 -04:00
EXTRACT_SUFX= .gem
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
# Ruby 1.9 and JRuby ship with ruby-gems
. if ${MODRUBY_REV} == 1.8
new depends
2010-11-17 03:05:12 -05:00
BUILD_DEPENDS+= devel/ruby-gems>=1.3.7p0
RUN_DEPENDS+= devel/ruby-gems>=1.3.7p0
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
. endif
# Just like all ruby C extensions should set SHARED_ONLY,
# pure ruby gem ports without C extensions should definitely not
# set SHARED_ONLY, and they are arch-independent.
. if !${CONFIGURE_STYLE:L:Mext}
. if defined(SHARED_ONLY) && ${SHARED_ONLY:L:Myes}
ERRORS+= "Fatal: Pure ruby gems without ext CONFIGURE_STYLE should not \
have SHARED_ONLY=Yes"
. endif
PKG_ARCH= *
. endif
# PLIST magic. Set variables so that the same PLIST will work for
# both ruby 1.8, ruby 1.9, and jruby.
SUBST_VARS+= ^GEM_LIB ^GEM_BIN DISTNAME
support for CONFIGURE_STYLE "ruby gem" with msf's consent
2006-06-11 15:56:31 -04:00
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
. if ${MODRUBY_REV} == jruby
GEM= ${RUBY} -S gem
Handle the gem metadata such that if a build fails and you restart it, it doesn't fail again just because it can't find the gem metadata. Also, get rid of the GEM_REL variable, and just setup the GEM_BIN and GEM_LIB variables separately for each ruby version. OK landry@
2010-12-01 20:38:40 -05:00
GEM_BIN = jruby/bin
GEM_LIB = jruby/lib/ruby/gems/${MODRUBY_LIBREV}
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
GEM_BASE_LIB= ${GEM_BASE}/jruby/${MODRUBY_LIBREV}
Allow building of rubinius versions of the ruby gem and extconf ports using the rbx FLAVOR and the rbx- package prefix. OK landry@, sthen@
2010-11-19 12:54:37 -05:00
. elif ${MODRUBY_REV} == rbx
GEM= ${RUBY} -S gem
GEM_BASE_LIB= ${GEM_BASE}/rbx/${MODRUBY_LIBREV}
Deal with the rubinius directory changes, and tie rbx FLAVORs to the currently supported minor version of rubinius. No longer allow a ruby18 FLAVOR to be used to specify ruby 1.8. Now, only the empty flavor should be used. OK landry@
2011-01-05 23:15:46 -05:00
GEM_BIN = lib/rubinius/gems/bin
GEM_LIB = lib/rubinius/gems/${MODRUBY_LIBREV}
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
. else
Split the lang/ruby port into separate ports for ruby 1.8 and ruby 1.9, similar to how the lang/python ports are handled. ruby 1.8 now installs as ruby18 and ruby 1.9 installs as ruby19. The included MESSAGE files for both ports let you know the symlinks to set up if you want to make that version the default system ruby. Split port originally started by bernd@, many changes since by me, help and support from jcs@, landry@, jasper@, and sthen@. This causes a large amount of fallout in dependent ruby ports, which will be committed shortly. OK jcs@, landry@, jasper@, sthen@
2010-09-23 17:58:50 -04:00
GEM= ${LOCALBASE}/bin/gem${MODRUBY_BINREV}
Handle the gem metadata such that if a build fails and you restart it, it doesn't fail again just because it can't find the gem metadata. Also, get rid of the GEM_REL variable, and just setup the GEM_BIN and GEM_LIB variables separately for each ruby version. OK landry@
2010-12-01 20:38:40 -05:00
GEM_BIN = bin
GEM_LIB = lib/ruby/gems/${MODRUBY_LIBREV}
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
GEM_BASE_LIB= ${GEM_BASE}/ruby/${MODRUBY_LIBREV}
. endif
Don't build C extensions inside gems during the fake stage, instead build them during the build stage and install them during fake. devel/ruby-gems doesn't have separate build and install commands, as most gems are pure ruby code and don't need a separate build stage. When ruby-gems is installing a gem with C extensions, it builds them during the install. Since installing is done during the fake stage, this meant that the extensions were getting built as root. Previously, this was required, as gem's --user-install option was broken. However, since that option has now been fixed, we use it to install the gem to a temporary location as the current user during build, and then mv and chown the files during fake. Thanks to bernd@ for pointing out that the fixed --user-install option allowed this. ok landry
2010-10-12 12:03:41 -04:00
GEM_BASE= ${WRKDIR}/gem-tmp/.gem
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
GEM_ABS_PATH= ${PREFIX}/${GEM_LIB}
GEM_BASE_BIN= ${GEM_BASE_LIB}/bin
# We purposely do not install documentation for ruby gems, because
# the filenames are generated differently on different ruby versions,
# and most use 1 file per method, which is insane.
GEM_FLAGS= --local --no-rdoc --no-ri --no-force --verbose --backtrace \
--user-install
Backout the ugly rev 1.12 hack. It's not needed anymore since we now have GEM_SKIPDEPENDS.
2007-11-13 12:32:59 -05:00
_GEM_CONTENT= ${WRKDIR}/gem-content
Add code that allows us to patch gem files. discussed with & ok sturm@ ok for an earlier version msf@
2006-10-18 09:41:36 -04:00
_GEM_DATAFILE= ${_GEM_CONTENT}/data.tar.gz
_GEM_PATCHED= ${DISTNAME}${EXTRACT_SUFX}
support for CONFIGURE_STYLE "ruby gem" with msf's consent
2006-06-11 15:56:31 -04:00
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
. if ${CONFIGURE_STYLE:L:Mformat-executable}
Split the lang/ruby port into separate ports for ruby 1.8 and ruby 1.9, similar to how the lang/python ports are handled. ruby 1.8 now installs as ruby18 and ruby 1.9 installs as ruby19. The included MESSAGE files for both ports let you know the symlinks to set up if you want to make that version the default system ruby. Split port originally started by bernd@, many changes since by me, help and support from jcs@, landry@, jasper@, and sthen@. This causes a large amount of fallout in dependent ruby ports, which will be committed shortly. OK jcs@, landry@, jasper@, sthen@
2010-09-23 17:58:50 -04:00
GEM_FLAGS+= --format-executable
Fix indentation and remove useless regress stuff comments. ok sturm@, msf@
2008-01-14 13:39:07 -05:00
. endif
Use the --skip-dependencies option with 'gem install' if GEM_SKIPDEPENDS is defined in the port Makefile. i.e. 'GEM_SKIPDEPENDS= hoe cgi_multipart_eof_fix' This will install the gem port into the fake area even if the hoe and cgi_multipart_eof_fix gems aren't installed. ok jcs@, "sounds reasonable but I haven't really looked at it" msf@
2007-11-13 11:10:37 -05:00
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
# Unpack the gem into WRKDIST so it can be patched. Include the gem metadata
# under WRKDIST so it can be patched easily to remove or change dependencies.
# Remove any signing of packages, as patching the gem could then break the
# signatures.
Fix various minor issues in ruby.port.mk: * No longer remove ruby-* from PKGNAME when building FULLPKGNAME for the gem and extconf ports * Correctly remove ruby18 FLAVOR * Use extract/build/install cookies * Fix installing of certain gems as root without systrace, by working around a bug in devel/ruby-gems * Remove MODRUBY_REV from SUBST_VARS OK landry@
2010-11-16 13:30:38 -05:00
${MODRUBY_EXTRACT_COOKIE}:
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
mkdir -p ${WRKDIST} ${_GEM_CONTENT}
cd ${_GEM_CONTENT} && tar -xf ${FULLDISTDIR}/${DISTNAME}${EXTRACT_SUFX}
cd ${WRKDIST} && tar -xzf ${_GEM_DATAFILE} && rm ${_GEM_DATAFILE}
Handle the gem metadata such that if a build fails and you restart it, it doesn't fail again just because it can't find the gem metadata. Also, get rid of the GEM_REL variable, and just setup the GEM_BIN and GEM_LIB variables separately for each ruby version. OK landry@
2010-12-01 20:38:40 -05:00
gzcat ${_GEM_CONTENT}/metadata.gz > ${WRKDIST}/.metadata
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
rm -f ${_GEM_CONTENT}/*.gz.sig
# Rebuild the gem manually after possible patching, then install it to a
# temporary directory (not the final directory under fake, since that would
# require root access and building C extensions as root).
Fix various minor issues in ruby.port.mk: * No longer remove ruby-* from PKGNAME when building FULLPKGNAME for the gem and extconf ports * Correctly remove ruby18 FLAVOR * Use extract/build/install cookies * Fix installing of certain gems as root without systrace, by working around a bug in devel/ruby-gems * Remove MODRUBY_REV from SUBST_VARS OK landry@
2010-11-16 13:30:38 -05:00
${MODRUBY_BUILD_COOKIE}:
Handle the gem metadata such that if a build fails and you restart it, it doesn't fail again just because it can't find the gem metadata. Also, get rid of the GEM_REL variable, and just setup the GEM_BIN and GEM_LIB variables separately for each ruby version. OK landry@
2010-12-01 20:38:40 -05:00
if [ -f ${WRKDIST}/.metadata ]; then \
cd ${WRKDIST} && gzip .metadata && \
mv .metadata.gz ${_GEM_CONTENT}/metadata.gz; \
fi
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
cd ${WRKDIST} && find . -type f \! -name '*.orig' -print | \
pax -wz -s '/^\.\///' -f ${_GEM_DATAFILE}
cd ${_GEM_CONTENT} && tar -cf ${WRKDIR}/${_GEM_PATCHED} *.gz
Don't build C extensions inside gems during the fake stage, instead build them during the build stage and install them during fake. devel/ruby-gems doesn't have separate build and install commands, as most gems are pure ruby code and don't need a separate build stage. When ruby-gems is installing a gem with C extensions, it builds them during the install. Since installing is done during the fake stage, this meant that the extensions were getting built as root. Previously, this was required, as gem's --user-install option was broken. However, since that option has now been fixed, we use it to install the gem to a temporary location as the current user during build, and then mv and chown the files during fake. Thanks to bernd@ for pointing out that the fixed --user-install option allowed this. ok landry
2010-10-12 12:03:41 -04:00
mkdir -p ${GEM_BASE}
Fix various minor issues in ruby.port.mk: * No longer remove ruby-* from PKGNAME when building FULLPKGNAME for the gem and extconf ports * Correctly remove ruby18 FLAVOR * Use extract/build/install cookies * Fix installing of certain gems as root without systrace, by working around a bug in devel/ruby-gems * Remove MODRUBY_REV from SUBST_VARS OK landry@
2010-11-16 13:30:38 -05:00
env -i ${MAKE_ENV} HOME=${GEM_BASE}/.. GEM_HOME=${GEM_BASE} \
Remove MODRUBY_PKGSPEC, rely on the PKGSPEC entries specified in lang/ruby/1.*/Makefile. Also, add the ability to pass CONFIGURE_ARGS to gem install. These get passed to the extconf.rb scripts that create the Makefiles for C extensions, and may make it easier to port gems with C extensions without resorting to patching. OK landry@
2010-11-24 16:30:36 -05:00
${GEM} install ${GEM_FLAGS} ${WRKDIR}/${_GEM_PATCHED} \
-- ${CONFIGURE_ARGS}
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
# Take the temporary gem directory, install the binary stub files to
# the appropriate directory, and move and fix ownership the gem library
# files.
Fix various minor issues in ruby.port.mk: * No longer remove ruby-* from PKGNAME when building FULLPKGNAME for the gem and extconf ports * Correctly remove ruby18 FLAVOR * Use extract/build/install cookies * Fix installing of certain gems as root without systrace, by working around a bug in devel/ruby-gems * Remove MODRUBY_REV from SUBST_VARS OK landry@
2010-11-16 13:30:38 -05:00
${MODRUBY_INSTALL_COOKIE}:
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
if [ -d ${GEM_BASE_BIN} ]; then \
${INSTALL_DATA_DIR} ${PREFIX}/${GEM_BIN}; \
Don't build C extensions inside gems during the fake stage, instead build them during the build stage and install them during fake. devel/ruby-gems doesn't have separate build and install commands, as most gems are pure ruby code and don't need a separate build stage. When ruby-gems is installing a gem with C extensions, it builds them during the install. Since installing is done during the fake stage, this meant that the extensions were getting built as root. Previously, this was required, as gem's --user-install option was broken. However, since that option has now been fixed, we use it to install the gem to a temporary location as the current user during build, and then mv and chown the files during fake. Thanks to bernd@ for pointing out that the fixed --user-install option allowed this. ok landry
2010-10-12 12:03:41 -04:00
for f in ${GEM_BASE_BIN}/*; do \
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
${INSTALL_SCRIPT} $$f ${PREFIX}/${GEM_BIN}; \
support for CONFIGURE_STYLE "ruby gem" with msf's consent
2006-06-11 15:56:31 -04:00
done; \
Delete the binaries after installing them into the fake directory but before copying the gem directory into the fake directory. Fixes update-plist adding files that shouldn't be in the resulting packages. ok landry
2010-10-15 16:24:27 -04:00
rm -r ${GEM_BASE_BIN}; \
support for CONFIGURE_STYLE "ruby gem" with msf's consent
2006-06-11 15:56:31 -04:00
fi
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
${INSTALL_DATA_DIR} ${GEM_ABS_PATH}
cd ${GEM_BASE_LIB} && mv * ${GEM_ABS_PATH}
chown -R ${SHAREOWN}:${SHAREGRP} ${GEM_ABS_PATH}
Fix various minor issues in ruby.port.mk: * No longer remove ruby-* from PKGNAME when building FULLPKGNAME for the gem and extconf ports * Correctly remove ruby18 FLAVOR * Use extract/build/install cookies * Fix installing of certain gems as root without systrace, by working around a bug in devel/ruby-gems * Remove MODRUBY_REV from SUBST_VARS OK landry@
2010-11-16 13:30:38 -05:00
. if !target(do-extract)
do-extract: ${MODRUBY_EXTRACT_COOKIE}
. endif
. if !target(do-build)
do-build: ${MODRUBY_BUILD_COOKIE}
support for CONFIGURE_STYLE "ruby gem" with msf's consent
2006-06-11 15:56:31 -04:00
. endif
Fix various minor issues in ruby.port.mk: * No longer remove ruby-* from PKGNAME when building FULLPKGNAME for the gem and extconf ports * Correctly remove ruby18 FLAVOR * Use extract/build/install cookies * Fix installing of certain gems as root without systrace, by working around a bug in devel/ruby-gems * Remove MODRUBY_REV from SUBST_VARS OK landry@
2010-11-16 13:30:38 -05:00
. if !target(do-install)
do-install: ${MODRUBY_INSTALL_COOKIE}
. endif
support for CONFIGURE_STYLE "ruby gem" with msf's consent
2006-06-11 15:56:31 -04:00
.elif ${CONFIGURE_STYLE:L:Msetup}
add CONFIGURE_STYLE "ruby setup" and related targets move LIB_DEPENDS to relevant ports, no PKGNAME bump needed this is in preparation of a soon to come ruby-gems port with msf's consent
2006-06-11 14:57:11 -04:00
MODRUBY_configure= \
cd ${WRKSRC}; ${SETENV} ${CONFIGURE_ENV} ${RUBY} setup.rb config \
--prefix=${PREFIX} ${CONFIGURE_ARGS};
Fix various minor issues in ruby.port.mk: * No longer remove ruby-* from PKGNAME when building FULLPKGNAME for the gem and extconf ports * Correctly remove ruby18 FLAVOR * Use extract/build/install cookies * Fix installing of certain gems as root without systrace, by working around a bug in devel/ruby-gems * Remove MODRUBY_REV from SUBST_VARS OK landry@
2010-11-16 13:30:38 -05:00
${MODRUBY_BUILD_COOKIE}:
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
cd ${WRKSRC} && ${SETENV} ${MAKE_ENV} ${RUBY} setup.rb setup
Fix various minor issues in ruby.port.mk: * No longer remove ruby-* from PKGNAME when building FULLPKGNAME for the gem and extconf ports * Correctly remove ruby18 FLAVOR * Use extract/build/install cookies * Fix installing of certain gems as root without systrace, by working around a bug in devel/ruby-gems * Remove MODRUBY_REV from SUBST_VARS OK landry@
2010-11-16 13:30:38 -05:00
${MODRUBY_INSTALL_COOKIE}:
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
cd ${WRKSRC} && ${SETENV} ${MAKE_ENV} ${RUBY} setup.rb install \
add CONFIGURE_STYLE "ruby setup" and related targets move LIB_DEPENDS to relevant ports, no PKGNAME bump needed this is in preparation of a soon to come ruby-gems port with msf's consent
2006-06-11 14:57:11 -04:00
--prefix=${DESTDIR}
Fix various minor issues in ruby.port.mk: * No longer remove ruby-* from PKGNAME when building FULLPKGNAME for the gem and extconf ports * Correctly remove ruby18 FLAVOR * Use extract/build/install cookies * Fix installing of certain gems as root without systrace, by working around a bug in devel/ruby-gems * Remove MODRUBY_REV from SUBST_VARS OK landry@
2010-11-16 13:30:38 -05:00
. if !target(do-build)
do-build: ${MODRUBY_BUILD_COOKIE}
. endif
. if !target(do-install)
do-install: ${MODRUBY_INSTALL_COOKIE}
add CONFIGURE_STYLE "ruby setup" and related targets move LIB_DEPENDS to relevant ports, no PKGNAME bump needed this is in preparation of a soon to come ruby-gems port with msf's consent
2006-06-11 14:57:11 -04:00
. endif
.endif
Add support for several popular ruby regression test suites accessible via the MODRUBY_REGRESS variable. discussed with and ok bernd@
2009-08-11 10:30:15 -04:00
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
# These are mostly used by the non-gem ports.
Remove MODRUBY_BIN_REV from SUBST_VARS, never used. OK landry@
2010-11-16 16:50:27 -05:00
SUBST_VARS+= MODRUBY_LIBREV MODRUBY_ARCH
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
Add support for several popular ruby regression test suites accessible via the MODRUBY_REGRESS variable. discussed with and ok bernd@
2009-08-11 10:30:15 -04:00
# regression stuff
.if !target(do-regress)
. if ${MODRUBY_REGRESS:L:Mrspec}
. if ${MODRUBY_REGRESS:L:Mrake}
Split the lang/ruby port into separate ports for ruby 1.8 and ruby 1.9, similar to how the lang/python ports are handled. ruby 1.8 now installs as ruby18 and ruby 1.9 installs as ruby19. The included MESSAGE files for both ports let you know the symlinks to set up if you want to make that version the default system ruby. Split port originally started by bernd@, many changes since by me, help and support from jcs@, landry@, jasper@, and sthen@. This causes a large amount of fallout in dependent ruby ports, which will be committed shortly. OK jcs@, landry@, jasper@, sthen@
2010-09-23 17:58:50 -04:00
RAKE_REGRESS_TARGET?= ${RSPEC_REGRESS_TARGET}
Add support for several popular ruby regression test suites accessible via the MODRUBY_REGRESS variable. discussed with and ok bernd@
2009-08-11 10:30:15 -04:00
. else
Split the lang/ruby port into separate ports for ruby 1.8 and ruby 1.9, similar to how the lang/python ports are handled. ruby 1.8 now installs as ruby18 and ruby 1.9 installs as ruby19. The included MESSAGE files for both ports let you know the symlinks to set up if you want to make that version the default system ruby. Split port originally started by bernd@, many changes since by me, help and support from jcs@, landry@, jasper@, and sthen@. This causes a large amount of fallout in dependent ruby ports, which will be committed shortly. OK jcs@, landry@, jasper@, sthen@
2010-09-23 17:58:50 -04:00
RSPEC_REGRESS_TARGET?= spec
Add support for several popular ruby regression test suites accessible via the MODRUBY_REGRESS variable. discussed with and ok bernd@
2009-08-11 10:30:15 -04:00
do-regress:
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
cd ${WRKSRC} && ${RSPEC} ${RSPEC_REGRESS_TARGET}
Add support for several popular ruby regression test suites accessible via the MODRUBY_REGRESS variable. discussed with and ok bernd@
2009-08-11 10:30:15 -04:00
. endif
. endif
. if ${MODRUBY_REGRESS:L:Mrake}
Split the lang/ruby port into separate ports for ruby 1.8 and ruby 1.9, similar to how the lang/python ports are handled. ruby 1.8 now installs as ruby18 and ruby 1.9 installs as ruby19. The included MESSAGE files for both ports let you know the symlinks to set up if you want to make that version the default system ruby. Split port originally started by bernd@, many changes since by me, help and support from jcs@, landry@, jasper@, and sthen@. This causes a large amount of fallout in dependent ruby ports, which will be committed shortly. OK jcs@, landry@, jasper@, sthen@
2010-09-23 17:58:50 -04:00
RAKE_REGRESS_TARGET?= test
Add support for several popular ruby regression test suites accessible via the MODRUBY_REGRESS variable. discussed with and ok bernd@
2009-08-11 10:30:15 -04:00
do-regress:
Major changes to allow the same port directory to build ports for both ruby 1.8, ruby 1.9, and jruby. One major change for all ports is that RDoc documentation is no longer going to be installed by default for gem ports. For ruby 1.8, it used a separate documentation file per method, and the file names created weren't consistent across ruby versions (1.8.6 differed from 1.8.7, and 1.8.7 differs from 1.9.2 and jruby). It made reviewing diffs very painful, and since most ruby developers do not use the documentation (preferring web documentation), it doesn't make sense to include them. For most gem ports, a ruby 1.9 version can be built by using the ruby19 FLAVOR, and a jruby version can be build using the jruby FLAVOR. These flavors modify the FULLPKGNAME to use either the ruby19- or jruby- package stem, so you don't need to worry about the ruby 1.8 package conflicting. In most cases, you no longer need the PKGNAME set in the port Makefile, as the FULLPKGNAME handling will take care of that for you. Also, for pure ruby gems (without C extensions), PKG_ARCH = * is added automatically. Changes to all dependent ports will be committed shortly. For new ruby ports, you need to make sure that gem dependencies are specified like this (assuming they depend on the hoe gem): :${MODRUBY_PKG_PREFIX}-hoe-*:devel/ruby-hoe,${FLAVOR} MODRUBY_PKG_PREFIX will be ruby for ruby 1.8 ports, ruby19 for ruby 1.9 ports, and jruby for jruby ports. The ,${FLAVOR} part at the end makes sure that dependencies use the same version of ruby that the current port uses. PLISTs are going to become a lot smaller with this. However, any binaries installed by the gem need to have a special string added. For example, the minitar binary installed by archivers/ruby-archive-tar-minitar looks like this in the PLIST: ${GEM_BIN}/minitar${GEM_BIN_SUFFIX} The ${GEM_BIN_SUFFIX} needs to be added manually so the package works on ruby 1.9, which installs the binaries with a 19 suffix. GEM_SKIPDEPENDS has been removed and related support will be removed from devel/ruby-gems. To modify dependencies inside the gem, the gem metadata is placed under WRKDIST and can be modified with the standard patching procedure. OK landry@
2010-11-08 18:20:43 -05:00
cd ${WRKSRC} && ${RAKE} ${RAKE_REGRESS_TARGET}
Add support for several popular ruby regression test suites accessible via the MODRUBY_REGRESS variable. discussed with and ok bernd@
2009-08-11 10:30:15 -04:00
. endif
. if !${MODRUBY_REGRESS:L:Mrspec} && !${MODRUBY_REGRESS:L:Mrake}
NO_REGRESS=YES
. endif
.endif
Reference in New Issue Copy Permalink