Date: Fri, 14 Jun 2002 15:58:08 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: Garrett Wollman <wollman@lcs.mit.edu>, "Akinori MUSHA" <knu@iDaemons.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: ports/Mk bsd.port.mk Message-ID: <p0511177bb92ff79cf8f6@[128.113.24.47]> In-Reply-To: <200206141811.g5EIBhND015735@khavrinen.lcs.mit.edu> References: <200206141102.50292.mi%2Bmx@aldan.algebra.com> <20020614113752.K11520-100000@blues.jpj.net> <86k7p16c4q.wl@archon.local.idaemons.org> <20020614101409.A88549@FreeBSD.ORG> <86hek56abw.wl@archon.local.idaemons.org> <200206141811.g5EIBhND015735@khavrinen.lcs.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
At 2:11 PM -0400 6/14/02, Garrett Wollman wrote: ><<On Sat, 15 Jun 2002, "Akinori MUSHA" <knu@iDaemons.org> said: > >> Juli Mallett wrote: >>> sed 's/foo/bar/;s/blah/bleh/' file | tee file > /dev/null > > > Surely that'll work, but it has to be a single command to > > be used in the ports infrastructure, no? > >It might work, but only by chance as a result of a race >condition and only on very small files. Hmm. Garrett's comment on small files reminded me of something. At some point in my past, I had to use perl to patch strings in some object files. For me, the issue was that sed was either truncating or "not scanning" very long lines. Whatever it was I was patching, it had those kinds of very long lines, and the result from using sed was a damaged file. Will our sed work correctly on files which have basically infinite-length "lines"? (when I ran into this, I am sure it was *not* on FreeBSD...) -- Garance Alistair Drosehn = gad@gilead.netel.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0511177bb92ff79cf8f6>