OpenOffice broken???

[stan]

On Fri, Apr 04, 2003 at 10:18:50AM -0500, Louis LeBlanc wrote:
> On 04/04/03 12:53 AM, mpd sat at the `puter and typed:
> > On Fri, Apr 04, 2003 at 02:14:09PM +1000, JacobRhoden wrote:
> > > On Fri, 4 Apr 2003 10:17 am, Louis LeBlanc wrote:
> > > > I've been running into a different problem than that one:
> > > >
> > > > ===>  Add wrapper scripts
> > > > sed: illegal option -- i
> > > > usage: sed script [-Ean] [file ...]
> > > >        sed [-an] [-e script] ... [-f script_file] ... [file ...]
> > > > *** Error code 1
> > > 
> > > jrhoden at elkanah# sed -h
> > > sed: illegal option -- h
> > > usage: sed script [-Ean] [-i extension] [file ...]
> > >        sed [-an] [-i extension] [-e script] ... [-f script_file] ... [file...]
> > > 
> > > It appears your version of sed is different than the one on my system (where 
> > > openoffice makes/installs fine. My version of sed comes from:
> > > 
> > >   FreeBSD elkanah.its.unimelb.edu.au 4.8-RC
> > >   FreeBSD 4.8-RC #1: Wed Mar 12 15:00:01 EST 2003     
> > > 
> > > I am guessing that your FreeBSD is older than that yes? 
> > > 
> > >  - jacob
> > 
> > In the past, the system sed didn't support the -i (edit file
> > in place) switch, but there is a port called sed_inplace
> > (textproc/sed_inplace) which handles it. If upgrading your base 
> > system (which I do recommend in your case) isn't an option,
> > this might work for you.
> > 
> > > 
> > > 
> > > Jacob Rhoden            Phone: +61 3 8344 6102
> > 
> > mike
> > -- 
> 
> Thanks Jacob and Mike.  I've actually been mulling the option of
> upgrading from 4.6, but I'm not sure which version I'd rather have.  I
> waited when 4.7 came out, then 4.8 . . .
> 
> My current install was built on 9/1/02 - just a version code update,
> not an OS update.  I almost upgraded then, but I was in the throes of
> a home purchase.  Not at my best, technically.
> 
> I'd welcome (and appreciate) version recommendations before I make my
> next upgrade.  What is generally considered the most stable release? I
> see a lot of problems on this list, but not much about the useability
> and stability - of course the list is supposed to be a place to get
> solutions to problem though, right?
> 

I have had great success following the STABLE branch using cvsup. I usually
upgrade almost every weekend. I have found thta upgrading more often
results in much less problems becuase each small change seems to work well.
Where I've had problems is when I waited to long to try to upgrade, and I
had many changes to apply.

-- 
"They that would give up essential liberty for temporary safety deserve
neither liberty nor safety."
						-- Benjamin Franklin