kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/misc/rubygems/rubygem.mk

171 lines
5.1 KiB
Makefile
Raw Normal View History

Skip printing "@dirrm lib/ruby/gems" in the print-PLIST output. Now, print-PLIST with USE_DESTDIR=full will generate the correct PLISTs for rubygems.
2008-03-12 21:27:08 +01:00
# $NetBSD: rubygem.mk,v 1.7 2008/03/12 20:27:08 jlam Exp $
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
#
# This Makefile fragment is intended to be included by packages that build
# and install Ruby gems.
#
+ Improve the documentation in the header of the rubygem.mk file. + Add a build dependency on rake, which is used to build a new gem file. Define RAKE to be the path to the installed rake binary. + Add "ruby" as a package category by default. + Define MASTER_SITES to a default value pointing to the main remote gem repository: http://gems.rubyforge.net/gems/. + Add a "do-gem-extract" target that extracts the files from the downloaded gem and into ${WRKSRC}. This allows us to patch or otherwise manipulate the files that are part of the gem that is to be installed. + Add a "do-gem-build" target that builds a new local gem from the contents of ${WRKSRC} using the provided Rakefile. This local gem which contains all pkgsrc modifications will be the one installed on the system. + Modify "do-gem-install" target to install from the new local gem created by the "do-gem-build" target. XXX The do-gem-install target still needs to use the new --buildroot XXX option to allow DESTDIR-style installations.
2008-03-12 05:06:15 +01:00
# Package-settable variables:
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
#
+ Improve the documentation in the header of the rubygem.mk file. + Add a build dependency on rake, which is used to build a new gem file. Define RAKE to be the path to the installed rake binary. + Add "ruby" as a package category by default. + Define MASTER_SITES to a default value pointing to the main remote gem repository: http://gems.rubyforge.net/gems/. + Add a "do-gem-extract" target that extracts the files from the downloaded gem and into ${WRKSRC}. This allows us to patch or otherwise manipulate the files that are part of the gem that is to be installed. + Add a "do-gem-build" target that builds a new local gem from the contents of ${WRKSRC} using the provided Rakefile. This local gem which contains all pkgsrc modifications will be the one installed on the system. + Modify "do-gem-install" target to install from the new local gem created by the "do-gem-build" target. XXX The do-gem-install target still needs to use the new --buildroot XXX option to allow DESTDIR-style installations.
2008-03-12 05:06:15 +01:00
# GEM_NAME
# The name of the gem to install. The default value is ${DISTNAME}.
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
#
+ Improve the documentation in the header of the rubygem.mk file. + Add a build dependency on rake, which is used to build a new gem file. Define RAKE to be the path to the installed rake binary. + Add "ruby" as a package category by default. + Define MASTER_SITES to a default value pointing to the main remote gem repository: http://gems.rubyforge.net/gems/. + Add a "do-gem-extract" target that extracts the files from the downloaded gem and into ${WRKSRC}. This allows us to patch or otherwise manipulate the files that are part of the gem that is to be installed. + Add a "do-gem-build" target that builds a new local gem from the contents of ${WRKSRC} using the provided Rakefile. This local gem which contains all pkgsrc modifications will be the one installed on the system. + Modify "do-gem-install" target to install from the new local gem created by the "do-gem-build" target. XXX The do-gem-install target still needs to use the new --buildroot XXX option to allow DESTDIR-style installations.
2008-03-12 05:06:15 +01:00
# GEMFILE
# The complete filename of the gem to install. It defaults to
# ${DISTNAME}.gem.
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
#
+ Improve the documentation in the header of the rubygem.mk file. + Add a build dependency on rake, which is used to build a new gem file. Define RAKE to be the path to the installed rake binary. + Add "ruby" as a package category by default. + Define MASTER_SITES to a default value pointing to the main remote gem repository: http://gems.rubyforge.net/gems/. + Add a "do-gem-extract" target that extracts the files from the downloaded gem and into ${WRKSRC}. This allows us to patch or otherwise manipulate the files that are part of the gem that is to be installed. + Add a "do-gem-build" target that builds a new local gem from the contents of ${WRKSRC} using the provided Rakefile. This local gem which contains all pkgsrc modifications will be the one installed on the system. + Modify "do-gem-install" target to install from the new local gem created by the "do-gem-build" target. XXX The do-gem-install target still needs to use the new --buildroot XXX option to allow DESTDIR-style installations.
2008-03-12 05:06:15 +01:00
# Variables defined in this file:
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
#
+ Improve the documentation in the header of the rubygem.mk file. + Add a build dependency on rake, which is used to build a new gem file. Define RAKE to be the path to the installed rake binary. + Add "ruby" as a package category by default. + Define MASTER_SITES to a default value pointing to the main remote gem repository: http://gems.rubyforge.net/gems/. + Add a "do-gem-extract" target that extracts the files from the downloaded gem and into ${WRKSRC}. This allows us to patch or otherwise manipulate the files that are part of the gem that is to be installed. + Add a "do-gem-build" target that builds a new local gem from the contents of ${WRKSRC} using the provided Rakefile. This local gem which contains all pkgsrc modifications will be the one installed on the system. + Modify "do-gem-install" target to install from the new local gem created by the "do-gem-build" target. XXX The do-gem-install target still needs to use the new --buildroot XXX option to allow DESTDIR-style installations.
2008-03-12 05:06:15 +01:00
# GEM_DOCDIR
# The path to the directory in the local gem repository that holds
# the documentation for the installed gem.
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
#
+ Improve the documentation in the header of the rubygem.mk file. + Add a build dependency on rake, which is used to build a new gem file. Define RAKE to be the path to the installed rake binary. + Add "ruby" as a package category by default. + Define MASTER_SITES to a default value pointing to the main remote gem repository: http://gems.rubyforge.net/gems/. + Add a "do-gem-extract" target that extracts the files from the downloaded gem and into ${WRKSRC}. This allows us to patch or otherwise manipulate the files that are part of the gem that is to be installed. + Add a "do-gem-build" target that builds a new local gem from the contents of ${WRKSRC} using the provided Rakefile. This local gem which contains all pkgsrc modifications will be the one installed on the system. + Modify "do-gem-install" target to install from the new local gem created by the "do-gem-build" target. XXX The do-gem-install target still needs to use the new --buildroot XXX option to allow DESTDIR-style installations.
2008-03-12 05:06:15 +01:00
# GEM_HOME
# The path to the local gem repository.
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
#
+ Improve the documentation in the header of the rubygem.mk file. + Add a build dependency on rake, which is used to build a new gem file. Define RAKE to be the path to the installed rake binary. + Add "ruby" as a package category by default. + Define MASTER_SITES to a default value pointing to the main remote gem repository: http://gems.rubyforge.net/gems/. + Add a "do-gem-extract" target that extracts the files from the downloaded gem and into ${WRKSRC}. This allows us to patch or otherwise manipulate the files that are part of the gem that is to be installed. + Add a "do-gem-build" target that builds a new local gem from the contents of ${WRKSRC} using the provided Rakefile. This local gem which contains all pkgsrc modifications will be the one installed on the system. + Modify "do-gem-install" target to install from the new local gem created by the "do-gem-build" target. XXX The do-gem-install target still needs to use the new --buildroot XXX option to allow DESTDIR-style installations.
2008-03-12 05:06:15 +01:00
# GEM_LIBDIR
# The path to the directory in the local gem repository that holds
# the contents of the installed gem.
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
#
+ Improve the documentation in the header of the rubygem.mk file. + Add a build dependency on rake, which is used to build a new gem file. Define RAKE to be the path to the installed rake binary. + Add "ruby" as a package category by default. + Define MASTER_SITES to a default value pointing to the main remote gem repository: http://gems.rubyforge.net/gems/. + Add a "do-gem-extract" target that extracts the files from the downloaded gem and into ${WRKSRC}. This allows us to patch or otherwise manipulate the files that are part of the gem that is to be installed. + Add a "do-gem-build" target that builds a new local gem from the contents of ${WRKSRC} using the provided Rakefile. This local gem which contains all pkgsrc modifications will be the one installed on the system. + Modify "do-gem-install" target to install from the new local gem created by the "do-gem-build" target. XXX The do-gem-install target still needs to use the new --buildroot XXX option to allow DESTDIR-style installations.
2008-03-12 05:06:15 +01:00
# RAKE
# The path to the ``rake'' binary.
#
# RUBYGEM_PKGPREFIX
# The recommended prefix for the PKGNAME.
#
# RUBYGEM
# The path to the rubygems ``gem'' script.
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
#
+ By default, support user-destdir installation as the gem installation process makes that easily possible. + Use ${EXTRACTOR} to manually unpack the gem file. + Change the do-gem-install target to initially build and install the gem into a buildroot, ${WRKDIR}/.inst, then to copy the files from the buildroot into the final install location, ${DESTDIR}${PREFIX}. XXX We still need to find some way to remove the intermediate build XXX files, e.g. *.o object files, from the buildroot before copying XXX to the final location.
2008-03-12 17:59:13 +01:00
# By default, assume that gems are capable of user-destdir installation.
PKG_DESTDIR_SUPPORT?= user-destdir
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
# Include this early in case some of its target are needed
.include "../../lang/ruby/modules.mk"
+ Improve the documentation in the header of the rubygem.mk file. + Add a build dependency on rake, which is used to build a new gem file. Define RAKE to be the path to the installed rake binary. + Add "ruby" as a package category by default. + Define MASTER_SITES to a default value pointing to the main remote gem repository: http://gems.rubyforge.net/gems/. + Add a "do-gem-extract" target that extracts the files from the downloaded gem and into ${WRKSRC}. This allows us to patch or otherwise manipulate the files that are part of the gem that is to be installed. + Add a "do-gem-build" target that builds a new local gem from the contents of ${WRKSRC} using the provided Rakefile. This local gem which contains all pkgsrc modifications will be the one installed on the system. + Modify "do-gem-install" target to install from the new local gem created by the "do-gem-build" target. XXX The do-gem-install target still needs to use the new --buildroot XXX option to allow DESTDIR-style installations.
2008-03-12 05:06:15 +01:00
# Build and run-time dependencies.
+ We need rubygems>=1.0.1nb1 (which has the OpenSuSE buildroot patch) for building and installing the gems, but we can use older rubygems at run-time. + Move GEMFILE definition ahead of EXTRACT_SUFX just as a style issue. This looks more like a normal package Makefile layout. + Rename GEMS_BASEDIR to GEM_HOME, which is the actual rubygems variable name for that directory. + Rename some variables to be more in line with other ruby variable names: GEM_LIB_DIR => GEM_LIBDIR GEM_DOC_DIR => GEM_DOCDIR + Set RUBYGEM_PKGPREFIX to ${RUBY_PKGPREFIX}-gem for now. We know that at least we don't want ruby packages to prefix with "rubygems". + Just use EVAL_PREFIX instead of directly using find-prefix.mk.
2008-03-11 23:11:32 +01:00
#
# We need rubygems>=1.0.1nb1 to actually build the package, but the
# resulting installed gem can run with older versions of rubygems.
#
+ Improve the documentation in the header of the rubygem.mk file. + Add a build dependency on rake, which is used to build a new gem file. Define RAKE to be the path to the installed rake binary. + Add "ruby" as a package category by default. + Define MASTER_SITES to a default value pointing to the main remote gem repository: http://gems.rubyforge.net/gems/. + Add a "do-gem-extract" target that extracts the files from the downloaded gem and into ${WRKSRC}. This allows us to patch or otherwise manipulate the files that are part of the gem that is to be installed. + Add a "do-gem-build" target that builds a new local gem from the contents of ${WRKSRC} using the provided Rakefile. This local gem which contains all pkgsrc modifications will be the one installed on the system. + Modify "do-gem-install" target to install from the new local gem created by the "do-gem-build" target. XXX The do-gem-install target still needs to use the new --buildroot XXX option to allow DESTDIR-style installations.
2008-03-12 05:06:15 +01:00
BUILD_DEPENDS+= rake-[0-9]*:../../devel/rake
+ We need rubygems>=1.0.1nb1 (which has the OpenSuSE buildroot patch) for building and installing the gems, but we can use older rubygems at run-time. + Move GEMFILE definition ahead of EXTRACT_SUFX just as a style issue. This looks more like a normal package Makefile layout. + Rename GEMS_BASEDIR to GEM_HOME, which is the actual rubygems variable name for that directory. + Rename some variables to be more in line with other ruby variable names: GEM_LIB_DIR => GEM_LIBDIR GEM_DOC_DIR => GEM_DOCDIR + Set RUBYGEM_PKGPREFIX to ${RUBY_PKGPREFIX}-gem for now. We know that at least we don't want ruby packages to prefix with "rubygems". + Just use EVAL_PREFIX instead of directly using find-prefix.mk.
2008-03-11 23:11:32 +01:00
BUILD_DEPENDS+= rubygems>=1.0.1nb1:../../misc/rubygems
DEPENDS+= rubygems>=0.8.7:../../misc/rubygems
# GEMFILE holds the filename of the Gem to install
.if defined(DISTFILES)
GEMFILE?= ${DISTFILES}
.else
GEMFILE?= ${DISTNAME}${EXTRACT_SUFX}
.endif
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
+ Improve the documentation in the header of the rubygem.mk file. + Add a build dependency on rake, which is used to build a new gem file. Define RAKE to be the path to the installed rake binary. + Add "ruby" as a package category by default. + Define MASTER_SITES to a default value pointing to the main remote gem repository: http://gems.rubyforge.net/gems/. + Add a "do-gem-extract" target that extracts the files from the downloaded gem and into ${WRKSRC}. This allows us to patch or otherwise manipulate the files that are part of the gem that is to be installed. + Add a "do-gem-build" target that builds a new local gem from the contents of ${WRKSRC} using the provided Rakefile. This local gem which contains all pkgsrc modifications will be the one installed on the system. + Modify "do-gem-install" target to install from the new local gem created by the "do-gem-build" target. XXX The do-gem-install target still needs to use the new --buildroot XXX option to allow DESTDIR-style installations.
2008-03-12 05:06:15 +01:00
CATEGORIES+= ruby
MASTER_SITES?= http://gems.rubyforge.org/gems/
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
EXTRACT_SUFX?= .gem
EXTRACT_ONLY?= # empty
# Base directory for Gems
+ We need rubygems>=1.0.1nb1 (which has the OpenSuSE buildroot patch) for building and installing the gems, but we can use older rubygems at run-time. + Move GEMFILE definition ahead of EXTRACT_SUFX just as a style issue. This looks more like a normal package Makefile layout. + Rename GEMS_BASEDIR to GEM_HOME, which is the actual rubygems variable name for that directory. + Rename some variables to be more in line with other ruby variable names: GEM_LIB_DIR => GEM_LIBDIR GEM_DOC_DIR => GEM_DOCDIR + Set RUBYGEM_PKGPREFIX to ${RUBY_PKGPREFIX}-gem for now. We know that at least we don't want ruby packages to prefix with "rubygems". + Just use EVAL_PREFIX instead of directly using find-prefix.mk.
2008-03-11 23:11:32 +01:00
GEM_HOME= ${PREFIX}/lib/ruby/gems/${RUBY_VER_DIR}
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
# Directory for the Gem to install
GEM_NAME?= ${DISTNAME}
+ We need rubygems>=1.0.1nb1 (which has the OpenSuSE buildroot patch) for building and installing the gems, but we can use older rubygems at run-time. + Move GEMFILE definition ahead of EXTRACT_SUFX just as a style issue. This looks more like a normal package Makefile layout. + Rename GEMS_BASEDIR to GEM_HOME, which is the actual rubygems variable name for that directory. + Rename some variables to be more in line with other ruby variable names: GEM_LIB_DIR => GEM_LIBDIR GEM_DOC_DIR => GEM_DOCDIR + Set RUBYGEM_PKGPREFIX to ${RUBY_PKGPREFIX}-gem for now. We know that at least we don't want ruby packages to prefix with "rubygems". + Just use EVAL_PREFIX instead of directly using find-prefix.mk.
2008-03-11 23:11:32 +01:00
GEM_LIBDIR= ${GEM_HOME}/gems/${GEM_NAME}
GEM_DOCDIR= ${GEM_HOME}/doc/${GEM_NAME}
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
+ We need rubygems>=1.0.1nb1 (which has the OpenSuSE buildroot patch) for building and installing the gems, but we can use older rubygems at run-time. + Move GEMFILE definition ahead of EXTRACT_SUFX just as a style issue. This looks more like a normal package Makefile layout. + Rename GEMS_BASEDIR to GEM_HOME, which is the actual rubygems variable name for that directory. + Rename some variables to be more in line with other ruby variable names: GEM_LIB_DIR => GEM_LIBDIR GEM_DOC_DIR => GEM_DOCDIR + Set RUBYGEM_PKGPREFIX to ${RUBY_PKGPREFIX}-gem for now. We know that at least we don't want ruby packages to prefix with "rubygems". + Just use EVAL_PREFIX instead of directly using find-prefix.mk.
2008-03-11 23:11:32 +01:00
RUBYGEM_PKGPREFIX= ${RUBY_PKGPREFIX}-gem
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
# RUBYGEM holds the path to RubyGems' gem command
+ We need rubygems>=1.0.1nb1 (which has the OpenSuSE buildroot patch) for building and installing the gems, but we can use older rubygems at run-time. + Move GEMFILE definition ahead of EXTRACT_SUFX just as a style issue. This looks more like a normal package Makefile layout. + Rename GEMS_BASEDIR to GEM_HOME, which is the actual rubygems variable name for that directory. + Rename some variables to be more in line with other ruby variable names: GEM_LIB_DIR => GEM_LIBDIR GEM_DOC_DIR => GEM_DOCDIR + Set RUBYGEM_PKGPREFIX to ${RUBY_PKGPREFIX}-gem for now. We know that at least we don't want ruby packages to prefix with "rubygems". + Just use EVAL_PREFIX instead of directly using find-prefix.mk.
2008-03-11 23:11:32 +01:00
EVAL_PREFIX+= RUBYGEM_PREFIX=rubygems
+ Improve the documentation in the header of the rubygem.mk file. + Add a build dependency on rake, which is used to build a new gem file. Define RAKE to be the path to the installed rake binary. + Add "ruby" as a package category by default. + Define MASTER_SITES to a default value pointing to the main remote gem repository: http://gems.rubyforge.net/gems/. + Add a "do-gem-extract" target that extracts the files from the downloaded gem and into ${WRKSRC}. This allows us to patch or otherwise manipulate the files that are part of the gem that is to be installed. + Add a "do-gem-build" target that builds a new local gem from the contents of ${WRKSRC} using the provided Rakefile. This local gem which contains all pkgsrc modifications will be the one installed on the system. + Modify "do-gem-install" target to install from the new local gem created by the "do-gem-build" target. XXX The do-gem-install target still needs to use the new --buildroot XXX option to allow DESTDIR-style installations.
2008-03-12 05:06:15 +01:00
EVAL_PREFIX+= RAKE_PREFIX=rake
RAKE= ${RAKE_PREFIX}/bin/rake
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
RUBYGEM= ${RUBYGEM_PREFIX}/bin/gem
# PLIST support
+ We need rubygems>=1.0.1nb1 (which has the OpenSuSE buildroot patch) for building and installing the gems, but we can use older rubygems at run-time. + Move GEMFILE definition ahead of EXTRACT_SUFX just as a style issue. This looks more like a normal package Makefile layout. + Rename GEMS_BASEDIR to GEM_HOME, which is the actual rubygems variable name for that directory. + Rename some variables to be more in line with other ruby variable names: GEM_LIB_DIR => GEM_LIBDIR GEM_DOC_DIR => GEM_DOCDIR + Set RUBYGEM_PKGPREFIX to ${RUBY_PKGPREFIX}-gem for now. We know that at least we don't want ruby packages to prefix with "rubygems". + Just use EVAL_PREFIX instead of directly using find-prefix.mk.
2008-03-11 23:11:32 +01:00
PLIST_SUBST+= GEM_HOME=${GEM_HOME:S|^${PREFIX}/||}
PLIST_SUBST+= GEM_LIBDIR=${GEM_LIBDIR:S|^${PREFIX}/||}
PLIST_SUBST+= GEM_DOCDIR=${GEM_DOCDIR:S|^${PREFIX}/||}
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
# print-PLIST support
+ We need rubygems>=1.0.1nb1 (which has the OpenSuSE buildroot patch) for building and installing the gems, but we can use older rubygems at run-time. + Move GEMFILE definition ahead of EXTRACT_SUFX just as a style issue. This looks more like a normal package Makefile layout. + Rename GEMS_BASEDIR to GEM_HOME, which is the actual rubygems variable name for that directory. + Rename some variables to be more in line with other ruby variable names: GEM_LIB_DIR => GEM_LIBDIR GEM_DOC_DIR => GEM_DOCDIR + Set RUBYGEM_PKGPREFIX to ${RUBY_PKGPREFIX}-gem for now. We know that at least we don't want ruby packages to prefix with "rubygems". + Just use EVAL_PREFIX instead of directly using find-prefix.mk.
2008-03-11 23:11:32 +01:00
PRINT_PLIST_AWK+= /^(@dirrm )?${GEM_LIBDIR:S|${PREFIX}/||:S|/|\\/|g}/ \
{ gsub(/${GEM_LIBDIR:S|${PREFIX}/||:S|/|\\/|g}/, "$${GEM_LIBDIR}"); print; next; }
PRINT_PLIST_AWK+= /^(@dirrm )?${GEM_DOCDIR:S|${PREFIX}/||:S|/|\\/|g}/ \
+ For print-PLIST, don't output any files or directories in ${GEM_DOCDIR} as those are automatically listed by RUBYGEM_GENERATE_PLIST. + Clean up the intermediate build files in the "ext" directory of installed gem by removing everything that's not also in the unpacked gem.
2008-03-12 19:53:35 +01:00
{ next; }
+ We need rubygems>=1.0.1nb1 (which has the OpenSuSE buildroot patch) for building and installing the gems, but we can use older rubygems at run-time. + Move GEMFILE definition ahead of EXTRACT_SUFX just as a style issue. This looks more like a normal package Makefile layout. + Rename GEMS_BASEDIR to GEM_HOME, which is the actual rubygems variable name for that directory. + Rename some variables to be more in line with other ruby variable names: GEM_LIB_DIR => GEM_LIBDIR GEM_DOC_DIR => GEM_DOCDIR + Set RUBYGEM_PKGPREFIX to ${RUBY_PKGPREFIX}-gem for now. We know that at least we don't want ruby packages to prefix with "rubygems". + Just use EVAL_PREFIX instead of directly using find-prefix.mk.
2008-03-11 23:11:32 +01:00
PRINT_PLIST_AWK+= /^@dirrm ${GEM_HOME:S|${PREFIX}/||:S|/|\\/|g}(\/(gems|cache|doc|specifications))?$$/ \
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
{ next; }
Skip printing "@dirrm lib/ruby/gems" in the print-PLIST output. Now, print-PLIST with USE_DESTDIR=full will generate the correct PLISTs for rubygems.
2008-03-12 21:27:08 +01:00
PRINT_PLIST_AWK+= /^@dirrm lib\/ruby\/gems$$/ { next; }
+ We need rubygems>=1.0.1nb1 (which has the OpenSuSE buildroot patch) for building and installing the gems, but we can use older rubygems at run-time. + Move GEMFILE definition ahead of EXTRACT_SUFX just as a style issue. This looks more like a normal package Makefile layout. + Rename GEMS_BASEDIR to GEM_HOME, which is the actual rubygems variable name for that directory. + Rename some variables to be more in line with other ruby variable names: GEM_LIB_DIR => GEM_LIBDIR GEM_DOC_DIR => GEM_DOCDIR + Set RUBYGEM_PKGPREFIX to ${RUBY_PKGPREFIX}-gem for now. We know that at least we don't want ruby packages to prefix with "rubygems". + Just use EVAL_PREFIX instead of directly using find-prefix.mk.
2008-03-11 23:11:32 +01:00
PRINT_PLIST_AWK+= /^(@dirrm )?${GEM_HOME:S|${PREFIX}/||:S|/|\\/|g}/ \
{ gsub(/${GEM_HOME:S|${PREFIX}/||:S|/|\\/|g}/, "$${GEM_HOME}"); print; next; }
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
+ Improve the documentation in the header of the rubygem.mk file. + Add a build dependency on rake, which is used to build a new gem file. Define RAKE to be the path to the installed rake binary. + Add "ruby" as a package category by default. + Define MASTER_SITES to a default value pointing to the main remote gem repository: http://gems.rubyforge.net/gems/. + Add a "do-gem-extract" target that extracts the files from the downloaded gem and into ${WRKSRC}. This allows us to patch or otherwise manipulate the files that are part of the gem that is to be installed. + Add a "do-gem-build" target that builds a new local gem from the contents of ${WRKSRC} using the provided Rakefile. This local gem which contains all pkgsrc modifications will be the one installed on the system. + Modify "do-gem-install" target to install from the new local gem created by the "do-gem-build" target. XXX The do-gem-install target still needs to use the new --buildroot XXX option to allow DESTDIR-style installations.
2008-03-12 05:06:15 +01:00
###
### do-gem-extract
###
### The do-gem-extract target extracts a standard gem file. A standard
### gem file contains:
###
### data.tar.gz contains the actual files to build, install, etc.
### metadata.gz YAML specification file
###
.PHONY: do-gem-extract
do-extract: do-gem-extract
do-gem-extract:
+ By default, support user-destdir installation as the gem installation process makes that easily possible. + Use ${EXTRACTOR} to manually unpack the gem file. + Change the do-gem-install target to initially build and install the gem into a buildroot, ${WRKDIR}/.inst, then to copy the files from the buildroot into the final install location, ${DESTDIR}${PREFIX}. XXX We still need to find some way to remove the intermediate build XXX files, e.g. *.o object files, from the buildroot before copying XXX to the final location.
2008-03-12 17:59:13 +01:00
${RUN} cd ${WRKDIR} && \
${EXTRACTOR} -f tar ${_DISTDIR:Q}/${GEMFILE:Q} data.tar.gz
+ Improve the documentation in the header of the rubygem.mk file. + Add a build dependency on rake, which is used to build a new gem file. Define RAKE to be the path to the installed rake binary. + Add "ruby" as a package category by default. + Define MASTER_SITES to a default value pointing to the main remote gem repository: http://gems.rubyforge.net/gems/. + Add a "do-gem-extract" target that extracts the files from the downloaded gem and into ${WRKSRC}. This allows us to patch or otherwise manipulate the files that are part of the gem that is to be installed. + Add a "do-gem-build" target that builds a new local gem from the contents of ${WRKSRC} using the provided Rakefile. This local gem which contains all pkgsrc modifications will be the one installed on the system. + Modify "do-gem-install" target to install from the new local gem created by the "do-gem-build" target. XXX The do-gem-install target still needs to use the new --buildroot XXX option to allow DESTDIR-style installations.
2008-03-12 05:06:15 +01:00
${RUN} mkdir ${WRKSRC}
+ By default, support user-destdir installation as the gem installation process makes that easily possible. + Use ${EXTRACTOR} to manually unpack the gem file. + Change the do-gem-install target to initially build and install the gem into a buildroot, ${WRKDIR}/.inst, then to copy the files from the buildroot into the final install location, ${DESTDIR}${PREFIX}. XXX We still need to find some way to remove the intermediate build XXX files, e.g. *.o object files, from the buildroot before copying XXX to the final location.
2008-03-12 17:59:13 +01:00
${RUN} cd ${WRKSRC} && \
${EXTRACTOR} -f tar ${WRKDIR:Q}/data.tar.gz
${RUN} rm -f ${WRKDIR:Q}/data.tar.gz
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
+ Improve the documentation in the header of the rubygem.mk file. + Add a build dependency on rake, which is used to build a new gem file. Define RAKE to be the path to the installed rake binary. + Add "ruby" as a package category by default. + Define MASTER_SITES to a default value pointing to the main remote gem repository: http://gems.rubyforge.net/gems/. + Add a "do-gem-extract" target that extracts the files from the downloaded gem and into ${WRKSRC}. This allows us to patch or otherwise manipulate the files that are part of the gem that is to be installed. + Add a "do-gem-build" target that builds a new local gem from the contents of ${WRKSRC} using the provided Rakefile. This local gem which contains all pkgsrc modifications will be the one installed on the system. + Modify "do-gem-install" target to install from the new local gem created by the "do-gem-build" target. XXX The do-gem-install target still needs to use the new --buildroot XXX option to allow DESTDIR-style installations.
2008-03-12 05:06:15 +01:00
###
### do-gem-build
###
### The do-gem-build target builds a new local gem from the extracted
### gem's contents. The new gem as created as ${WRKSRC}/pkg/${GEMFILE}.
###
.PHONY: do-gem-build
do-build: do-gem-build
do-gem-build:
${RUN} cd ${WRKSRC} && ${SETENV} ${MAKE_ENV} ${RAKE} gem
###
### do-gem-install
###
### The do-gem-install target installs the local gem in ${WRKDIR} into
+ By default, support user-destdir installation as the gem installation process makes that easily possible. + Use ${EXTRACTOR} to manually unpack the gem file. + Change the do-gem-install target to initially build and install the gem into a buildroot, ${WRKDIR}/.inst, then to copy the files from the buildroot into the final install location, ${DESTDIR}${PREFIX}. XXX We still need to find some way to remove the intermediate build XXX files, e.g. *.o object files, from the buildroot before copying XXX to the final location.
2008-03-12 17:59:13 +01:00
### the gem repository. We this this as a staged installation
### (independent of PKG_DESTDIR_SUPPORT) because it can potentially
### build software and we want that to happen within ${WRKDIR}.
+ Improve the documentation in the header of the rubygem.mk file. + Add a build dependency on rake, which is used to build a new gem file. Define RAKE to be the path to the installed rake binary. + Add "ruby" as a package category by default. + Define MASTER_SITES to a default value pointing to the main remote gem repository: http://gems.rubyforge.net/gems/. + Add a "do-gem-extract" target that extracts the files from the downloaded gem and into ${WRKSRC}. This allows us to patch or otherwise manipulate the files that are part of the gem that is to be installed. + Add a "do-gem-build" target that builds a new local gem from the contents of ${WRKSRC} using the provided Rakefile. This local gem which contains all pkgsrc modifications will be the one installed on the system. + Modify "do-gem-install" target to install from the new local gem created by the "do-gem-build" target. XXX The do-gem-install target still needs to use the new --buildroot XXX option to allow DESTDIR-style installations.
2008-03-12 05:06:15 +01:00
###
+ By default, support user-destdir installation as the gem installation process makes that easily possible. + Use ${EXTRACTOR} to manually unpack the gem file. + Change the do-gem-install target to initially build and install the gem into a buildroot, ${WRKDIR}/.inst, then to copy the files from the buildroot into the final install location, ${DESTDIR}${PREFIX}. XXX We still need to find some way to remove the intermediate build XXX files, e.g. *.o object files, from the buildroot before copying XXX to the final location.
2008-03-12 17:59:13 +01:00
_RUBYGEM_BUILDROOT= ${WRKDIR}/.inst
_RUBYGEM_OPTIONS= --no-update-sources # don't cache the gem index
_RUBYGEM_OPTIONS+= --install-dir ${GEM_HOME}
_RUBYGEM_OPTIONS+= --build-root ${_RUBYGEM_BUILDROOT}
_RUBYGEM_OPTIONS+= --local ${WRKSRC}/pkg/${GEMFILE}
_RUBYGEM_OPTIONS+= -- --build-args ${CONFIGURE_ARGS}
GENERATE_PLIST+= ${RUBYGEM_GENERATE_PLIST}
RUBYGEM_GENERATE_PLIST= \
${ECHO} "@comment The following lines are automatically generated." && \
( cd ${_RUBYGEM_BUILDROOT}${PREFIX} && \
${FIND} ${GEM_DOCDIR:S|${PREFIX}/||} \! -type d -print | \
${SORT} && \
${FIND} ${GEM_DOCDIR:S|${PREFIX}/||} -type d -print | \
${SORT} -r | ${SED} -e "s,^,@dirrm ," );
+ Improve the documentation in the header of the rubygem.mk file. + Add a build dependency on rake, which is used to build a new gem file. Define RAKE to be the path to the installed rake binary. + Add "ruby" as a package category by default. + Define MASTER_SITES to a default value pointing to the main remote gem repository: http://gems.rubyforge.net/gems/. + Add a "do-gem-extract" target that extracts the files from the downloaded gem and into ${WRKSRC}. This allows us to patch or otherwise manipulate the files that are part of the gem that is to be installed. + Add a "do-gem-build" target that builds a new local gem from the contents of ${WRKSRC} using the provided Rakefile. This local gem which contains all pkgsrc modifications will be the one installed on the system. + Modify "do-gem-install" target to install from the new local gem created by the "do-gem-build" target. XXX The do-gem-install target still needs to use the new --buildroot XXX option to allow DESTDIR-style installations.
2008-03-12 05:06:15 +01:00
.PHONY: do-gem-install
As discussed on tech-pkg@ add a Makefile fragment intended to help packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-11 21:12:17 +01:00
do-install: do-gem-install
+ Improve the documentation in the header of the rubygem.mk file. + Add a build dependency on rake, which is used to build a new gem file. Define RAKE to be the path to the installed rake binary. + Add "ruby" as a package category by default. + Define MASTER_SITES to a default value pointing to the main remote gem repository: http://gems.rubyforge.net/gems/. + Add a "do-gem-extract" target that extracts the files from the downloaded gem and into ${WRKSRC}. This allows us to patch or otherwise manipulate the files that are part of the gem that is to be installed. + Add a "do-gem-build" target that builds a new local gem from the contents of ${WRKSRC} using the provided Rakefile. This local gem which contains all pkgsrc modifications will be the one installed on the system. + Modify "do-gem-install" target to install from the new local gem created by the "do-gem-build" target. XXX The do-gem-install target still needs to use the new --buildroot XXX option to allow DESTDIR-style installations.
2008-03-12 05:06:15 +01:00
do-gem-install:
+ By default, support user-destdir installation as the gem installation process makes that easily possible. + Use ${EXTRACTOR} to manually unpack the gem file. + Change the do-gem-install target to initially build and install the gem into a buildroot, ${WRKDIR}/.inst, then to copy the files from the buildroot into the final install location, ${DESTDIR}${PREFIX}. XXX We still need to find some way to remove the intermediate build XXX files, e.g. *.o object files, from the buildroot before copying XXX to the final location.
2008-03-12 17:59:13 +01:00
@${STEP_MSG} "Installing gem into buildroot"
${RUN} ${SETENV} ${INSTALL_ENV} ${MAKE_ENV} \
${RUBYGEM} install ${_RUBYGEM_OPTIONS}
Don't try to remove the intermediate build files unless the ext/ directory exists.
2008-03-12 21:08:22 +01:00
${RUN} if [ -d ${_RUBYGEM_BUILDROOT}${GEM_LIBDIR}/ext ]; then \
cd ${_RUBYGEM_BUILDROOT}${GEM_LIBDIR}/ext && ls | \
while read file; do \
if [ ! -f ${WRKSRC}/ext/$$file ]; then \
echo "rm "${GEM_LIBDIR:T}"/ext/$$file"; \
rm -f $$file; \
fi; \
done; \
fi
+ By default, support user-destdir installation as the gem installation process makes that easily possible. + Use ${EXTRACTOR} to manually unpack the gem file. + Change the do-gem-install target to initially build and install the gem into a buildroot, ${WRKDIR}/.inst, then to copy the files from the buildroot into the final install location, ${DESTDIR}${PREFIX}. XXX We still need to find some way to remove the intermediate build XXX files, e.g. *.o object files, from the buildroot before copying XXX to the final location.
2008-03-12 17:59:13 +01:00
@${STEP_MSG} "Copying files into installation directory"
${RUN} cd ${_RUBYGEM_BUILDROOT}${PREFIX} && \
pax -rwpe . ${DESTDIR}${PREFIX}
Reference in a new issue Copy permalink