From owner-freebsd-stable Wed Oct 9 22:57:51 2002 Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 85C3537B401 for ; Wed, 9 Oct 2002 22:57:49 -0700 (PDT) Received: from vectors.cx (manifold.vectors.cx [64.163.147.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id 25ECF43E6E for ; Wed, 9 Oct 2002 22:57:49 -0700 (PDT) (envelope-from monkey@vectors.cx) Received: from vectors.cx (e52b711e73106e7fefe5176c48410f2b@localhost [127.0.0.1]) by vectors.cx (8.12.6/8.12.4) with ESMTP id g9A5wuho057650; Wed, 9 Oct 2002 22:58:56 -0700 (PDT) (envelope-from monkey@vectors.cx) Received: (from monkey@localhost) by vectors.cx (8.12.6/8.12.6/Submit) id g9A5wuFD057649; Wed, 9 Oct 2002 22:58:56 -0700 (PDT) (envelope-from monkey) Date: Wed, 9 Oct 2002 22:58:55 -0700 From: Adam Weinberger To: Yoshinori KASAZAKI Cc: dsyphers@uchicago.edu, freebsd-stable@FreeBSD.ORG Subject: Re: New sed breaks ports Message-ID: <20021010055855.GQ81796@vectors.cx> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021010144447.090ec5c3.mia@gold.ocn.ne.jp> X-Editor: Vim 6.1 http://www.vim.org X-Mailer: Mutt 1.5 http://www.mutt.org X-URL: http://www.vectors.cx http://www.crackula.com User-Agent: Mutt/1.5.1i Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >> (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 << 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. this is a probem of you not using sed the right way. read sed(1). 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. -Adam -- "Oh good, my dog found the chainsaw." -Lilo, "Lilo & Stitch" Adam Weinberger adam@vectors.cx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message