From owner-freebsd-ruby@FreeBSD.ORG  Tue Jun 12 00:26:41 2012
Return-Path: <owner-freebsd-ruby@FreeBSD.ORG>
Delivered-To: ruby@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id B1FA7106566B
	for <ruby@freebsd.org>; Tue, 12 Jun 2012 00:26:41 +0000 (UTC)
	(envelope-from stas@FreeBSD.org)
Received: from mx0.deglitch.com (cl-414.sto-01.se.sixxs.net
	[IPv6:2001:16d8:ff00:19d::2])
	by mx1.freebsd.org (Postfix) with ESMTP id 607D28FC12
	for <ruby@freebsd.org>; Tue, 12 Jun 2012 00:26:41 +0000 (UTC)
Received: from orion.swifttest.com (unknown [74.3.97.52])
	by mx0.deglitch.com (Postfix) with ESMTPA id 53C5B8FC27;
	Tue, 12 Jun 2012 04:26:40 +0400 (MSK)
Received: from orion.swifttest.com (localhost [127.0.0.1])
	by orion.swifttest.com (Postfix) with SMTP id 768615C50;
	Mon, 11 Jun 2012 17:26:35 -0700 (PDT)
Date: Mon, 11 Jun 2012 17:26:35 -0700
From: Stanislav Sedov <stas@FreeBSD.org>
To: =?KOI8-R?Q?=FA=CC=C1=D4=CB=CF_=E1=D3=C5=CE=CF=D7?=
	<zlatko.asenov@gmail.com>
Message-Id: <20120611172635.03dba3d1.stas@FreeBSD.org>
In-Reply-To: <4FD65FBE.8070909@gmail.com>
References: <4FD5A6AD.4060303@gmail.com>
	<4FD65FBE.8070909@gmail.com>
Organization: The FreeBSD Project
X-Mailer: carrier-pigeon
Mime-Version: 1.0
Content-Type: text/plain; charset=KOI8-R
Content-Transfer-Encoding: quoted-printable
Cc: ruby@freebsd.org
Subject: Re: [Solved]  ExecJS::RuntimeError in Demo#index
X-BeenThere: freebsd-ruby@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: FreeBSD-specific Ruby discussions <freebsd-ruby.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ruby>,
	<mailto:freebsd-ruby-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ruby>
List-Post: <mailto:freebsd-ruby@freebsd.org>
List-Help: <mailto:freebsd-ruby-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ruby>,
	<mailto:freebsd-ruby-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Jun 2012 00:26:41 -0000

On Tue, 12 Jun 2012 00:14:38 +0300
=FA=CC=C1=D4=CB=CF =E1=D3=C5=CE=CF=D7 <zlatko.asenov@gmail.com> mentioned:

> Hi All,
>=20
> I resolved the issue.
>=20
> What I did:
>=20
> 1. # pkg_deinstall -r rubygem\*
>=20
> Didn't help.
>=20
> 2. # portmaster --force-config www/node and unchecked  SHARED_V8 option.
>=20
> 3. #  portmaster devel/ruby-gems
>=20
> 4. #  gem install rails
>=20
> Now it works :)
>=20
> If I may ask a question: Is it better to install gems from ports or=20
> using the 'gem install' method?
>=20

Personally, I'd recommend using gems (at least for development).
This way you will get the updates faster, and will be able to
have multiple version of a gem installed, which sometimes is required
by some libraries.  Also, tools like 'bundle' utilize gems system
as well.

BTW, you can have gems installed locally for a particular user while
having ports managing the system-wide gems.  They won't interfere.
Just set the GEM_HOME variable to point to a place where you want
gems to be installed.

--=20
Stanislav Sedov
ST4096-RIPE

()  ascii ribbon campaign - against html e-mail=20
/\  www.asciiribbon.org   - against proprietary attachments