Date: Thu, 10 Oct 2002 12:40:03 -0400 From: Bill Moran <wmoran@potentialtech.com> To: Adam Weinberger <adam@vectors.cx> Cc: Yoshinori KASAZAKI <mia@gold.ocn.ne.jp>, dsyphers@uchicago.edu, freebsd-stable@FreeBSD.ORG Subject: Re: New sed breaks ports Message-ID: <3DA5AD63.2010801@potentialtech.com> References: <20021009210042.A3027@klentaq.com> <20021010040550.2539c6f2.corecode@corecode.ath.cx> <20021009211658.A3071@klentaq.com> <200210092131.11605.dsyphers@uchicago.edu> <20021010144447.090ec5c3.mia@gold.ocn.ne.jp> <20021010055855.GQ81796@vectors.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
Adam Weinberger wrote: >>>(10.09.2002 @ 2244 PST): Yoshinori KASAZAKI said, in 1.2K: << >> >>I get following ... >> >> >>>sed -i >> >>sed: option requires an argument -- i >>usage: sed script [-Ean] [-i extension] [file ...] >> sed [-an] [-i extension] [-e script] ... [-f script_file] ... [file ...] >> >>>sed -i foo >> >>sed: -i may not be used with stdin >> >>If this is the case, it seems like sed is invoked without extension. >>(I don't know why, though...) >> >>>end of "Re: New sed breaks ports" from Yoshinori KASAZAKI << I'm really confused by the answers I'm getting here. > this is not a problem with an out-of-date ports tree. this is not a > problem with your source tree. this is not a problem with the wrong > version of sed being installed. Good. > this is a probem of you not using sed the right way. I'm not using sed. I know almost nothing about sed. I type "cd /usr/ports/editors/openoffice; make" and I get this error. _I_ am not the one using sed incorrectly. If anything, the port maintainer is. > read sed(1). Honestly, with my schedule, if I need to learn sed in order to install OpenOffice, then I'll keep using StarOffice for the the time being. I'm not trying to be rude here, it's just that I'm confused about these answers. Are people hinting that I should fix the port, or is my problem simply being misinterpreted? All I was trying to do was a test install of OpenOffice to see if it was in good enough shape to replace StarOffice. The fact that the port failed is an indicator to me that it's NOT ready. Now, all I'm trying to do is provide enough information so that I'm a useful debugger to whomever will fix the port. The complicated part is that other people claim that OpenOffice installed without a hitch, and I'm trying to figure out if _I_ did something wrong or if there's a hidden factor that should be documented (i.e. something I should do with my system before installing that I wasn't aware of) > sed -i edits a file in-place. you can't edit stdin in-place. sed -i foo > says to edit whatever file you didn't specify, and save a backup with > extension .foo. > > your sed is working properly. Great, what isn't then? -- Bill Moran Potential Technologies http://www.potentialtech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3DA5AD63.2010801>