You are viewing a plain text version of this content. The canonical link for it is here.
Posted to qa@openoffice.apache.org by Zack Glennie <za...@gmail.com> on 2012/11/20 10:07:22 UTC
Is it really dangerous to run the Dev version of AOO on my main workstation?
The Apache pages warn against running Dev-AOO on a production machine, and
suggest a spare computer or virtualization through Virtualbox.
In my current situation, core OS corruption would be inconvenient but not
disastrous. I am tempted to just run Dev-AOO directly. If am comfortable
doing this if the odds of OS corruption are less than 1% per week (or,
around 1% per 10 hours of using AOO).
So, given this level of risk tolerance, should I install Dev-AOO directly?
Zack
--
tel:+972 054 2914692
http://zglen.com
Re: Is it really dangerous to run the Dev version of AOO on my main workstation?
Posted by Ji Yan <ya...@gmail.com>.
Hi Zark,
You can try AOO-Dev build on your machine directly, I don't think
application will crash your system.
2012/11/20 Zack Glennie <za...@gmail.com>
> The Apache pages warn against running Dev-AOO on a production machine, and
> suggest a spare computer or virtualization through Virtualbox.
>
> In my current situation, core OS corruption would be inconvenient but not
> disastrous. I am tempted to just run Dev-AOO directly. If am comfortable
> doing this if the odds of OS corruption are less than 1% per week (or,
> around 1% per 10 hours of using AOO).
>
> So, given this level of risk tolerance, should I install Dev-AOO directly?
>
> Zack
>
> --
> tel:+972 054 2914692
> http://zglen.com
>
--
Thanks & Best Regards, Yan Ji
Re: Is it really dangerous to run the Dev version of AOO on my main workstation?
Posted by Zack Glennie <za...@gmail.com>.
Excellent, thank you!
On Tue, Nov 20, 2012 at 4:42 PM, Rob Weir <ro...@apache.org> wrote:
> On Tue, Nov 20, 2012 at 4:07 AM, Zack Glennie <za...@gmail.com>
> wrote:
> > The Apache pages warn against running Dev-AOO on a production machine,
> and
> > suggest a spare computer or virtualization through Virtualbox.
> >
> > In my current situation, core OS corruption would be inconvenient but not
> > disastrous. I am tempted to just run Dev-AOO directly. If am comfortable
> > doing this if the odds of OS corruption are less than 1% per week (or,
> > around 1% per 10 hours of using AOO).
> >
>
> OS-corruption would be very rare. More likely would be corrupting
> your AOO install. When this happens a normal uninstall of the
> application may not work. You might need to manually clean up the
> installation, delete the OpenOffice profile directory, etc. Using a
> VM makes this kind of cleanup trivial, since you can quickly roll back
> to a clean OS image. So you are always starting from a well-defined
> state.
>
> Occasional problems you'll run into are AOO crashes and writing out
> corrupted documents. That is why you want to avoid doing "real work"
> on a test build. You don't want to risk editing important personal or
> business documents on a test build.
>
> > So, given this level of risk tolerance, should I install Dev-AOO
> directly?
> >
>
> I think the risk of OS corruption is very low.
>
> -Rob
>
>
> > Zack
> >
> > --
> > tel:+972 054 2914692
> > http://zglen.com
>
--
tel:+972 054 2914692
http://zglen.com
Re: Is it really dangerous to run the Dev version of AOO on my main workstation?
Posted by Rob Weir <ro...@apache.org>.
On Tue, Nov 20, 2012 at 4:07 AM, Zack Glennie <za...@gmail.com> wrote:
> The Apache pages warn against running Dev-AOO on a production machine, and
> suggest a spare computer or virtualization through Virtualbox.
>
> In my current situation, core OS corruption would be inconvenient but not
> disastrous. I am tempted to just run Dev-AOO directly. If am comfortable
> doing this if the odds of OS corruption are less than 1% per week (or,
> around 1% per 10 hours of using AOO).
>
OS-corruption would be very rare. More likely would be corrupting
your AOO install. When this happens a normal uninstall of the
application may not work. You might need to manually clean up the
installation, delete the OpenOffice profile directory, etc. Using a
VM makes this kind of cleanup trivial, since you can quickly roll back
to a clean OS image. So you are always starting from a well-defined
state.
Occasional problems you'll run into are AOO crashes and writing out
corrupted documents. That is why you want to avoid doing "real work"
on a test build. You don't want to risk editing important personal or
business documents on a test build.
> So, given this level of risk tolerance, should I install Dev-AOO directly?
>
I think the risk of OS corruption is very low.
-Rob
> Zack
>
> --
> tel:+972 054 2914692
> http://zglen.com