On Thu, Dec 17, 2009 at 2:51 PM, Troels Kofoed Jacobsen <tkjacob...@gmail.com> wrote: > On Thu, Dec 17, 2009 at 8:11 AM, Troels Kofoed Jacobsen > <tkjacob...@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 before, >>> and >>> I know about the s command, and how it sets it's delimiters. Â Anyhow, >>> here's the >>> broken line, and I hope my mailer doesn't decide to break the line for me: >>> >>> REINPLACE_ARGS= -i.bak -E -e "1s,^(\#!.* )python$$,\1 -S >>> PYTHONPATH=${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?= -i.bak this also confirms that your -i.bak is not a problem! -- Med Venlig Hilsen Troels Kofoed Jacobsen _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"