Date: Thu, 17 Dec 2009 14:56:24 +0100 From: Troels Kofoed Jacobsen <tkjacobsen@gmail.com> To: freebsd-ports@freebsd.org Subject: Re: trying to fix a sed line Message-ID: <6a3173850912170556x34d0c4d2y7abaa0ee31bc62ce@mail.gmail.com> In-Reply-To: <6a3173850912170551r238b051dg4c4b76f4f2ad9c86@mail.gmail.com> References: <4B295701.2000908@telenix.org> <20091217071106.GA1401@photon.std> <6a3173850912170551r238b051dg4c4b76f4f2ad9c86@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Dec 17, 2009 at 2:51 PM, Troels Kofoed Jacobsen
<tkjacobsen@gmail.com> wrote:
> On Thu, Dec 17, 2009 at 8:11 AM, Troels Kofoed Jacobsen
> <tkjacobsen@gmail.com> wrote:
>> On Wed, Dec 16, 2009 at 04:54:09PM -0500, Chuck Robey wrote:
>>> I don't do enough in sed .... if I could figure out what it is that the=
broken
>>> line is TRYING to do, I think maybe I could fix it, I HAVE used sed bef=
ore, and
>>> I know about the s command, and how it sets it's delimiters. =A0Anyhow,=
here's the
>>> broken line, and I hope my mailer doesn't decide to break the line for =
me:
>>>
>>> REINPLACE_ARGS=3D -i.bak -E -e "1s,^(\#!.* )python$$,\1 -S PYTHONPATH=
=3D${DATADIR}
>>> ${PYTHON_CMD},1"
>
> It could also be a problem that REINPLACE_CMD expands to "sed -i" or
> something like this, but you also give it the same flag!
>
> /Troels Kofoed Jacobsen
>
Forget what I just said:
Mk/bsd.port.mk:
REINPLACE_ARGS?=3D -i.bak
this also confirms that your -i.bak is not a problem!
--=20
Med Venlig Hilsen
Troels Kofoed Jacobsen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6a3173850912170556x34d0c4d2y7abaa0ee31bc62ce>