Date: Sun, 8 Sep 2002 09:31:14 -0500 From: David Syphers <dsyphers@uchicago.edu> To: "Simon 'corecode' Schubert" <corecode@corecode.ath.cx> Cc: kris@obsecurity.org, ports@FreeBSD.ORG Subject: Re: sed -i Message-ID: <200209080931.14018.dsyphers@uchicago.edu> In-Reply-To: <20020908045641.54899254.corecode@corecode.ath.cx> References: <200209062332.54123.dsyphers@uchicago.edu> <200209070017.09053.dsyphers@uchicago.edu> <20020908045641.54899254.corecode@corecode.ath.cx>
next in thread | previous in thread | raw e-mail | index | archive | help
On Saturday 07 September 2002 09:56 pm, Simon 'corecode' Schubert wrote: > On Sat, 7 Sep 2002 00:17:09 -0500 David Syphers wrote: > > > > The sed_inplace port was created for precisely this purpose. Your > > > ports collection _should_ be using it, if it's completely up-to-date. > > Is there something I need to do other than cvsup? (I do this regularly.) The > > only things not in my cvsup file are foreign languages, palm, and picobsd. > > the first thing to do is either update your whole system to -stable or > revert your kernel back to -release. this has been the cause for this > very problem several times now: > osversion is being checked in bsd.port.mk to check whether sed_inplace > is needed or not. if you are using -release everything should work fine. > if you're using -stable, you don't have to worry because sed can cope > with -i then. As I said in an email that was bounced from ports@ because "Message content rejected", I am running my package builds in a sandbox. The sandbox is 4.6.2-R, because that's the environment of the machine I'm installing these programs on. My computer, on the other hand, is running -stable. I have to use a sandbox because 'make package' irritatingly needs to install a package to build it, and many of the packages I'm trying to build are already installed on my machine. I'm sorry this isn't a supported configuration, but there is a hack that works - install sed_inplace manually, remove /usr/bin/sed, and replace it with a link to /usr/local/bin/sed_inplace. Thanks for helping me understand why my configuration caused this problem to be particularly nasty. Now I just hope this message isn't rejected :) -David -- When ideas fail, words come in very handy. -Goethe Astronomy and Astrophysics Center The University of Chicago To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200209080931.14018.dsyphers>