| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
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.
|
|
They have security problems and are not maintained.
Removal was announced on pkgsrc-users on March 13.
|
|
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.
|
|
|
|
|
|
+ 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.
|
|
Bump PKGREVISION. Pointed out by drochner@ in private e-mail.
|
|
make that the default version required for dependencies.
+ Same deal for rake>=0.8.1.
|
|
of the install phase. The whole point of "buildroot" was to avoid
building anything in the install phase.
|
|
possibility of a name collision with a file named "metadata".
|
|
gem during the build process. This allows for specifying non-standard
tasks used by some Ruby packages. It defaults to "gem".
|
|
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.
|
|
intermediate build files. GEM_CLEANBUILD now defaults to "ext/*".
|
|
value a bit.
|
|
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.
|
|
unpacked sources. This fixes certain checks for $HOME, $PATH and the
like.
|
|
+ Note bin/screen as a setuid-root program using SPECIAL_PERMS.
Bump the PKGREVISION to 1.
|
|
|
|
Bump PKGREVISION.
|
|
extraction procedures can be handled by this file.
|
|
|
|
+ The local gem is not ${GEMFILE}; it's ${GEM_NAME}.gem. The two can
be different due to capitalization/case differences.
|
|
+ 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/).
|
|
now.
|
|
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.
|
|
|
|
|
|
looking through the ext/ directory structure. Not all gems are simple.
|
|
|
|
|
|
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.
|
|
|
|
${PKGVERSION} instead.
|
|
Now, print-PLIST with USE_DESTDIR=full will generate the correct
PLISTs for rubygems.
|
|
exists.
|
|
${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.
|
|
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.
|
|
+ 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.
|
|
packaging RubyGems.
Its functionality is somewhat limited for now but will be without
doubt improved and refactored in the very near future.
|
|
changes:
-added, updated and improved hacks
-bugfixes
-Reworked PAM code to support fingerprint readers, etc.
-Minor tweaks for compilation on MacOS 10.5.0
|
|
|
|
dvtm brings the concept of tiling window management, popularized by X11-window
managers like dwm to the console. As a console window manager it tries to make
it easy to work with multiple console based programs like vim, mutt, cmus or
irssi.
Packaged by Leonardo Taccari in pkgsrc-wip.
|
|
|
|
|
|
|
