patches to add it). Drop pax from the default USE_TOOLS list.
Make bsdtar the default for those places that wanted gtar to extract
long links etc, as bsdtar can be built of the tree.
* 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.
+ 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.
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.
+ 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.
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.
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.
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.
+ 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.
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/).
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.
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.
${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.
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.
+ 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.
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.
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.
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
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.
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.
Major changes since 0.9.0:
* RubyGems no longer allows installation of files outside the gem directory
* #require_gem will now print a warning, use #gem instead
* RubyGems now requires ruby 1.8.2 or greater
* RubyGems is -w clean
* The "unpack" command now works properly.
* User name and password are now passed properly to the authenticating
proxy when downloading gems.
* Improved dependency checks and installation via gems.
* .gemrc now allows setting default options per gem sub-command.
* Wrappers and/or symlinks are created as needd to put executables
into the ruby bindir.
* Creating and checking digital signatures on gems.
RubyGems is a way to package Ruby libraries/applications for
distribution, its a distribution manager, its a package manager.
RubyGems brings to the world of Ruby a very valuable capability--the
ability to manage concurrent versions of libraries and dependencies
between those libraries. This last aspect of RubyGems is one of the
most important to the end user, because its value is continuous as you
use and program Ruby, but to understand its impact an explanation of
how Ruby manages libraries is in order.
