Date: Sun, 8 Sep 2002 02:46:19 -0400 From: parv <parv_fm@emailgroups.net> To: David Syphers <dsyphers@uchicago.edu> Cc: ports@freebsd.org Subject: Re: sed -i Message-ID: <20020908064619.GA90399@moo.holy.cow> In-Reply-To: <200209071506.42351.dsyphers@uchicago.edu> References: <200209062332.54123.dsyphers@uchicago.edu> <200209070017.09053.dsyphers@uchicago.edu> <20020907155135.GA88171@moo.holy.cow> <200209071506.42351.dsyphers@uchicago.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
in message <200209071506.42351.dsyphers@uchicago.edu>, wrote David Syphers thusly... > > On Saturday 07 September 2002 10:51 am, parv wrote: > > ... either you can leave sed_inplace alone & it will be built > > when another port needs it; or, explicitly build it yourself. ... > After installing sed_inplace manually, I still had the exact same > problem. I had to manually remove /usr/bin/sed and replace it with > a link to /usr/local/bin/sed_inplace. I should note that I'm > running these package builds in a 4.6.2 sandbox, but I can't see > how that would make a difference. yikes, that's one horrendus situation to be in. :( sorry, i can't add more meaningfull... i wish there might be a cleaner solution... - parv -- 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?20020908064619.GA90399>