./devel/ruby-therubyracer [embeds the V8 javascript interpreter into ruby]
[+] Add this package to your ports tracker

[ CVSweb ] [ Homepage ] [ RSS feed ]

Version: 0.12.3, Package name: therubyracer-0.12.3
Maintained by: The OpenBSD ports mailing-list
Master sites:
Flavors (export FLAVOR=xyz, setenv FLAVOR xyz):
  • ruby27
  • ruby30
  • ruby31
Description
Embed the V8 Javascript interpreter into Ruby. Features:

* Evaluate Javascript from within Ruby
* Embed your Ruby objects into the Javascript world
* Manipulate JavaScript objects and call JavaScript functions from Ruby

Filesize: 57.5 KB
Version History (View Complete History)
  • (2017-11-05) Updated to version: therubyracer-0.12.3
  • (2012-12-13) Package added to openports.se, version therubyracer-0.11.0 (created)
[show/hide] View available PLISTS (Can be a lot of data)

CVS Commit History:

   2019-07-12 14:46:30 by Stuart Henderson | Files touched by this commit (853)
Log message:
replace simple PERMIT_PACKAGE_CDROM=Yes with PERMIT_PACKAGE=Yes
   2018-10-24 08:28:14 by Stuart Henderson | Files touched by this commit (740)
Log message:
Add COMPILER lines to c++ ports which currently use the default. Adjust
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
   2018-06-13 16:26:53 by Jeremy Evans | Files touched by this commit (49)
Log message:
Add OpenBSD comment to rubygems-ext.PLIST
Bump ruby gem ext ports as this changes the package.
Requested by espie@
   2017-07-26 16:45:35 by Stuart Henderson | Files touched by this commit (937)
Log message:
bump LIBCXX/LIBECXX/COMPILER_LIBCXX ports.
   2017-07-16 13:19:06 by Marc Espie | Files touched by this commit (880)
Log message:
use COMPILER_LIBCXX where applicable
   2017-04-10 05:45:29 by Stuart Henderson | Files touched by this commit (281)
Log message:
use LIBCXX
   2017-03-24 07:35:23 by Aaron Bieber | Files touched by this commit (1)
Log message:
mark therubyracer as broken
It requires a super old version of libv8 and is preventing major updates to
other applications (including security updates)
If soneone wants to use therubyracer, I suggest having it build with an
internal version of v8.
Discussed with landry@ and jeremy@
   2016-11-04 15:26:38 by Jeremy Evans | Files touched by this commit (27)
Log message:
Bump ruby gem ext ports after change to PLISTs
This does not include all ruby gem ext ports, but the remaining ones have
updates that will be committed separately.
   2014-10-17 11:03:27 by Jasper Lievisse Adriaanse | Files touched by this commit (12)
Log message:
disable rspec2 tests for these ports as rspec2 will be removed shortly.
ok jeremy@