summaryrefslogtreecommitdiff
path: root/misc/rubygems
AgeCommit message (Collapse)AuthorFilesLines
2008-04-13Update misc/rubygems to 1.1.1. Changes from version 1.1.0 include:jlam5-41/+41
* Gem.prefix now returns non-nil only when RubyGems was installed outside sitelibdir or libdir. * The `gem server` gem list now correctly links to gem details. * `gem update --system` now passes --no-format-executable to setup.rb. * Gem::SourceIndex#refresh! now works with multiple gem repositories. * Downloaded gems now go into --install-dir's cache directory. * Various fixes to downloading gem metadata. * `gem install --force` now ignores network errors too. * `gem pristine` now rebuilds extensions. * `gem update --system` now works on virgin Apple ruby. * Gem::RemoteFetcher handles Errno::ECONNABORTED.
2008-03-31Set up the shell environment before calling ``gem'' during the extractjlam1-4/+5
phase. Also set TZ to null to prevent timezone differences from affecting the printing of the "date" field during the extraction of the gemspec file.
2008-03-31Update rubygems to 1.1.0. Changes from version 1.0.1 include:jlam12-154/+227
+ Port patches to allow gems to be installed into an "installion root" from 1.0.1nb2. + Rename the --build-root option to --install-root, which more accurately reflects the purpose of the option. + Update rubygem.mk to work with rubygems-1.1.0. + Require 1.1.0 as the minimum rubygems version for the build. + Remove GEM_FORMAT and special code to extract the gemspec file from a gem archive -- `gem spec' can now do it correctly by itself. + Rename various *buildroot* targets to *install-root* to match the name of the `gem' option. * RubyGems now uses persistent connections on index updates and only updates from a latest index by default, cutting candidate gems for updates to roughly 1/4 (at present). Index updates are much faster now. * `gem list -r` may only show the latest version of a gem, add --all to see all gems. * `gem spec` now extracts specifications from .gem files. * `gem query --installed` to aid automation of checking for gems. This update has been tested with the 3 packages in pkgsrc that install using the ``gem'' command: devel/rubyforge misc/ruby-gem_plugin www/mongrel This update has also been tested with the 129 packages in my local tree that install using the ``gem'' command.
2008-03-27Use the correct variable name (GEM_CACHEDIR, not GEM_CACHE).jlam1-3/+3
2008-03-27The ``gem'' command doesn't exit with an error if the install fails.jlam1-1/+14
Manually check that the installation actually succeeds or exit with an error so that the pkgsrc make process halts with the proper error code. Suggestion for change by <seb> in private email.
2008-03-24Restore default setting of PKG_DESTDIR_SUPPORT removed in revisionjlam1-1/+4
1.29. This does the right thing automatically for most gems, and packages that need PKG_DESTDIR_SUPPORT set earlier can set it manually themselves.
2008-03-22Add default value for GEM_FORMAT missing from previous commit.jlam1-1/+4
2008-03-21Update description to be less rambling and more consise.jlam1-8/+6
2008-03-21+ Drop the GEMFILE variable which is completely unused.jlam1-25/+48
+ Add a GEM_SPECFILE variable which points to the gemspec file to use when building using the ``gemspec'' GEM_BUILD method. It defaults to ${WRKDIR}/${DISTNAME}.gemspec. + Add a GEM_FORMAT variable that indicates the archive format of the downloaded gem. Possible are "packed" and "tar" with a default of "tar". "Packed" is the old gem-0.8.x format, while "tar" is the current one. + Make gem-extract a dependency for post-extract, not do-extract. This allows for the usual do-extract actions to take place in the case where EXTRACT_SUFX is not ".gem". Now, if any of the DISTFILES are gems, then gem-extract takes care of all of the extraction, but otherwise, the usual do-extract actions take place. + Use the gem script to unpack the downloaded gem. We still have to manually extract the gemspec file, but at least we make fewer assumptions about the format of the gem.
2008-03-21Remove PKG_DESTDIR_SUPPORT setting from rubygem.mk. Its placement injlam1-4/+1
this file was awkward because PKG_DESTDIR_SUPPORT must be set before the first inclusion of bsd.prefs.mk, which forced rubygem.mk to be included before any other file. Instead, packages which install as Ruby gems should define PKG_DESTDIR_SUPPORT on their own.
2008-03-19+ About half of the gems I've touched have required rubygems>=1.0.1, sojlam1-3/+3
make that the default version required for dependencies. + Same deal for rake>=0.8.1.
2008-03-19+ Move the "install into buildroot" step into the build phase and outjlam1-46/+45
of the install phase. The whole point of "buildroot" was to avoid building anything in the install phase.
2008-03-18Extract the gemspec file before the data.tar.gz so that we avoid anyjlam1-2/+2
possibility of a name collision with a file named "metadata".
2008-03-18Use ${BUILD_TARGET} as the Rakefile task invoked to create the localjlam1-2/+10
gem during the build process. This allows for specifying non-standard tasks used by some Ruby packages. It defaults to "gem".
2008-03-18Fix subtle interaction with DESTDIR during installation -- the Makefilesjlam1-2/+2
generated by mkmf.rb are actually not DESTDIR-safe because the $(DESTDIR) value gets propagated to the rpath. Since we already pass --buildroot to deal with staged installations, explicitly strip out DESTDIR from the environment.
2008-03-18Unify the two clauses in _gem-install-cleanbuild that removed thejlam1-24/+17
intermediate build files. GEM_CLEANBUILD now defaults to "ext/*".
2008-03-18REPLACE_RUBY_DIRS is relative to ${WRKSRC} by default, so shorten thejlam1-2/+2
value a bit.
2008-03-18Installed gems have wrapper scripts that call the right interpreter,jlam1-1/+7
regardless of the #! line at the head of a script, so we can skip the interpreter path check for gems. As a side benefit, the resulting gems are more suitable for distribution to other platforms.
2008-03-17Pass MAKE_ENV to the build process when building the gem from thejlam1-3/+4
unpacked sources. This fixes certain checks for $HOME, $PATH and the like.
2008-03-14Allow for gem-extract to be overridden so that packages with specialjlam1-1/+3
extraction procedures can be handled by this file.
2008-03-14+ Add an example value for GEM_CLEANBUILD.jlam1-1/+5
2008-03-14+ Minor improvements to documentation.jlam1-10/+10
+ The local gem is not ${GEMFILE}; it's ${GEM_NAME}.gem. The two can be different due to capitalization/case differences.
2008-03-14+ Rename the metadata (gemspec) file to a more sensible name (*.gemspec).jlam1-5/+9
+ Clean up additional unpacked bits (*.sig) files during extraction. + Fix the "cleanbuild" step: + In GEM_CLEANBUILD case, sanity check that the file doesn't exist in the unpacked gem before removing it from the installed gem. + Actually removes unwanted directories.
2008-03-13+ Modify gem-rake-build to find the generated .gem file in the eventjlam1-2/+29
that the Rakefile creates it in a non-standard place. + Create a new variable GEM_CLEANBUILD which is a list of globs for files to remove from the gem installed in the buildroot in the _gem-install-cleanbuild target. This allows for packages with a non-standard gem directory structure (one that has the .c files under ext/).
2008-03-13Rename PLIST.common to PLIST as we just use the standard PLIST mechanismjlam1-1/+1
now.
2008-03-13+ Rename some variables and modify a few definitions so that we matchjlam1-26/+22
the same variables used in rubygem.mk. + Use a GENERATE_PLIST statement instead of manually generating a PLIST_DYNAMIC file. This code is copied from RUBYGEM_GENERATE_PLIST in rubygem.mk. + Use INSTALL_ENV, which is meant to contain the extra environment bits for use during installation.
2008-03-13Most gems need at least rubygems-0.9.4 to work properly.jlam1-2/+2
2008-03-13Whitespacify to be easier on my eyes.jlam1-14/+14
2008-03-13When cleaning out the intermediate build files, be more thorough aboutjlam1-4/+9
looking through the ext/ directory structure. Not all gems are simple.
2008-03-13For brevity, rename the do-gem-* targets to just "gem-*".jlam1-18/+18
2008-03-13Split the do-gem-install target into smaller sub-targets.jlam1-4/+17
2008-03-13+ Add a package-settable variable GEM_BUILD that sets the way thatjlam1-13/+35
the local gem that is installed is built from the extracted sources. The possible values are "gemspec" and "rake", with "rake" being the default. + Change the do-gem-extract target so that it also extracts the gemspec file from the source gem. This gemspec file is used when the "gemspec" GEM_BUILD method is chosen. + Add do-gem-${GEM_BUILD}-targets that build the local gem using the corresponding ${GEM_BUILD} method.
2008-03-12Make RUBYGEM_PKGPREFIX the same as RUBY_PKGPREFIX.jlam1-2/+2
2008-03-12Don't hardcode the package version number into the PLIST -- usejlam1-1/+3
${PKGVERSION} instead.
2008-03-12Skip printing "@dirrm lib/ruby/gems" in the print-PLIST output.jlam1-1/+2
Now, print-PLIST with USE_DESTDIR=full will generate the correct PLISTs for rubygems.
2008-03-12Don't try to remove the intermediate build files unless the ext/ directoryjlam1-9/+10
exists.
2008-03-12+ For print-PLIST, don't output any files or directories injlam1-2/+10
${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+ By default, support user-destdir installation as the gem installationjlam1-12/+35
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-12Fix bug in the interaction between --build-root and --remote noted in:jlam3-6/+25
http://rubyforge.org/pipermail/rubygems-developers/2006-June/002010.html If --build-root is specified, then any remote gems are now downloaded into the "cache" directory under the buildroot. Bump PKGREVISION to 2.
2008-03-12+ Improve the documentation in the header of the rubygem.mk file.jlam1-25/+72
+ 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-11+ We need rubygems>=1.0.1nb1 (which has the OpenSuSE buildroot patch)jlam1-27/+30
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-11As discussed on tech-pkg@ add a Makefile fragment intended to helpseb1-0/+87
packaging RubyGems. Its functionality is somewhat limited for now but will be without doubt improved and refactored in the very near future.
2008-03-08Don't hardcode "1.8" in the GEM_SUBDIR -- use ${RUBY_VER_DIR} instead.jlam1-2/+2
2008-03-08+ Add patches by Marcus Rueckert for destdir-style installation of gems.jlam9-860/+187
Patches from the OpenSuSE rubygems-1.0.1 src rpm. + Support user-destdir installation. + Dynamically generate the entire portion of the PLIST that corresponds to the documentation generated by rubygem at install-time. Bump the PKGREVISION to 1.
2008-01-16Update rubygems to 1.0.1.minskim4-23/+26
Major New Features Include: * RubyGems warns about various problems with gemspecs during gem building * More-consistent versioning for the RubyGems software Other Changes Include: * Fixed various bugs and problems with installing gems on Windows * Fixed using `gem server` for installing gems * Various operations are even more verbose with --verbose * Built gems are now backwards compatible with 0.9.4 * Improved detection of RUBYOPT loading rubygems * `ruby setup.rb` now has a --help option * Gem::Specification#bindir is now respected on installation * Executable stubs can now be installed to match ruby's name, so if ruby is installed as 'ruby18', foo_exec will be installed as 'foo_exec18' * `gem unpack` can now unpack into a specific directory with --target * OpenSSL is no longer required by default
2007-12-13Use more Ruby specific name: s/REPLACE_FILE_PAT/REPLACE_RUBY_PAT/.taca1-2/+2
2007-12-03Remove entries that are automatically included in PLIST.minskim1-707/+1
Noted by Filip Hajny in a private email.
2007-12-02Update to rubygems to 0.9.5.minskim4-147/+901
New features: * Automatic installation of platform gems * New bandwidth and memory friendlier index file format * "Offline" mode (--no-update-sources) * Bulk update threshold can be specified (-B, --bulk-threshold) * New `gem fetch` command * `gem` now has "really verbose" output when you specify -v * Ruby 1.9 compatible See http://rubyforge.org/frs/shownotes.php?release_id=16500 for the complete list.
2007-05-30Update rubygems to 0.9.4.minskim3-8/+10
Changes: * Several people have been experiencing problems with no method errors on the source index cache. The source index cache is now a bit more self healing. Furthermore, if the source index cache is irreparable, then it is automatically dropped and reloaded. * The source cache files may now be dropped with the "gem sources --clear-all" command. (This command may require root is the system source cache is in a root protected area). * Several sub-commands were accidently dropped from the "gem" command. These commands have been restored.
2007-05-23Update rubygems to 0.9.3.minskim5-1444/+906
This is a maintenance release of RubyGems that fixs a problem with ZLib on Windows platforms.
generated by cgit v1.2.3 (git 2.39.1) at 2025-01-01 22:34:46 +0000