Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 6 Nov 2008 13:48:57 +0300
From:      Stanislav Sedov <stas@FreeBSD.org>
To:        Daniel Roethlisberger <daniel@roe.ch>
Cc:        freebsd-ruby@freebsd.org
Subject:   Re: Patches to rubygem ports
Message-ID:  <20081106134857.edbc19dd.stas@FreeBSD.org>
In-Reply-To: <20081105233843.GH33630@hobbes.ustdmz.roe.ch>
References:  <20081105233843.GH33630@hobbes.ustdmz.roe.ch>

next in thread | previous in thread | raw e-mail | index | archive | help
--Signature=_Thu__6_Nov_2008_13_48_57_+0300_TSJ_lbSNllTcVmD7
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, 6 Nov 2008 00:38:43 +0100
Daniel Roethlisberger <daniel@roe.ch> mentioned:

> I maintain a rubygem port which needs a bit of gentle patching to
> get it to work fully.  Since rubygem based ports do not unpack
> any sources into work, what is the `official' way to patch files
> contained in the rubygem?  Adding files/patch-* will fail because
> there is no unpacked source directory...
>=20

I don't think there's an easy way of doing this. Once I had to do the
same task and ended with applying the patch by hand in the post-install
stage. Ugly enough, but it worked.

--=20
Stanislav Sedov
ST4096-RIPE

--Signature=_Thu__6_Nov_2008_13_48_57_+0300_TSJ_lbSNllTcVmD7
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (FreeBSD)

iEYEARECAAYFAkkSy58ACgkQK/VZk+smlYHHEgCePL87KNa2AEGh8wjSsdPuladi
1wcAn25jrjH6UqS9pzHJCB5L2Be+e1BH
=3OJy
-----END PGP SIGNATURE-----

--Signature=_Thu__6_Nov_2008_13_48_57_+0300_TSJ_lbSNllTcVmD7--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20081106134857.edbc19dd.stas>