From daniel at roe.ch Wed Nov 5 15:42:00 2008 From: daniel at roe.ch (Daniel Roethlisberger) Date: Wed Nov 5 15:42:07 2008 Subject: Patches to rubygem ports Message-ID: <20081105233843.GH33630@hobbes.ustdmz.roe.ch> 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... -- Daniel Roethlisberger http://daniel.roe.ch/ From stas at FreeBSD.org Thu Nov 6 02:34:40 2008 From: stas at FreeBSD.org (Stanislav Sedov) Date: Thu Nov 6 02:34:47 2008 Subject: Patches to rubygem ports In-Reply-To: <20081105233843.GH33630@hobbes.ustdmz.roe.ch> References: <20081105233843.GH33630@hobbes.ustdmz.roe.ch> Message-ID: <20081106134857.edbc19dd.stas@FreeBSD.org> On Thu, 6 Nov 2008 00:38:43 +0100 Daniel Roethlisberger 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... > 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. -- Stanislav Sedov ST4096-RIPE -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 195 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-ruby/attachments/20081106/266630b6/attachment.pgp