Hi,

some of you have already noticed that the OpenOffice.org package is finally 
built for older products by the Build Service. The packages are available at

http://software.opensuse.org/download/OpenOffice.org/openSUSE_10.2/
http://software.opensuse.org/download/OpenOffice.org/SUSE_Linux_10.1/
http://software.opensuse.org/download/OpenOffice.org/SUSE_Linux_10.0/
http://software.opensuse.org/download/OpenOffice.org/SLED_10/


Let me to answer some potential question. I hope that the FAQ style would be 
better readable.


Q: What sources are used?
A: The packages are based on the latest sources from FACTORY and rebuilt for 
older products. The current packages are based on OOo-2.2.1rc1.


Q: Are there any differences against FACTORY?
A: There are some few features that cannot be built on older products. For 
example, the gstreamer on SL 10.0 is too old, so the audio/video support 
cannot be enabled there.


Q: How often will OOo be updated?
A: I usually update the OOo package in FACTORY every two weeks. There might be 
bigger delay in the early development phase of a openSUSE or SLED. There might 
be more often updates close before the release the products.

There might be another delays caused by build issues. There are still some
problems with the build machines. The openSUSE team is working on it. Another 
problems might be caused by the package itself. I will always try to fix them 
within the next submit, so you should have a newer version at least once each 
month.


Q: What is the stability?
A: The stability of the package will vary over the time. In general, it should 
be very stable close before the openSUSE release. It might be less stable 
otherwise.

The current version should be in a good shape because it is based on quite 
stable upstream sources and also on quite stable Novell changes. The 
situation might be totally different in a month when I plan to update to the 
upstream OOo-2.3 development snapshot and use also the latest Novell changes.


Q: Is it possible to find somewhere an older "good" build when the current one 
is not usable?
A: Currently no. I heard that the GNOME project had the same problem. We are 
waiting for an official support from the Build Service framework. We hope 
that it will support making snapshots in the future.


Q: How is this build supported by Novell?
A: This build is not officially supported by Novell. We will be happy if you 
report bugs, see below. Though, it might take longer time until the bugs are 
fixed, especially if they happen only on older products.

Note that I do only some basic checks in FACTORY. I am sorry, I can't do this 
checks on all older distributions with every update. We are going to add some 
automatic test during build, so we might quarantee a bigger quality in the 
future (hopefully within next 2 months).


Q: Where can I ask questions regarding OOo?
A: I am sorry, even if I find more time for you, I can't answer everything. I 
would sort the questions into the following categories:
        + general questions about OOo (about a functionality) should be best
          answered by the OOo community on [EMAIL PROTECTED]
        + bugs should be reported into bugzilla, see below
        + other questions about our plans, Novell features, ... should be
          send to this list. Please mention "OpenOffice.org or OOo somewhere
          in the Subject. I promise, I'll take more care of this list and
          answer OOo-related questions at least once or twice a week. If I
          don't, feel free to CC me ;-)


Q: How to report bugs?
A: Please, report bugs at https://bugzilla.novell.com for the 
product "OpenOffice.org 2.0".

Please, do not forget to mention:
        + that the package is from the Build Service
        + system you are running, e.g. "openSUSE-10.2-x86_64"
        + desktop you are using, e.g. KDE, GNOME
        + OOo version from the last line of the dialog "Help/About 
OpenOffice.org",
          e.g. "Build 2.2.0.1"
        + that you are running 32-bit OOo on x86_64 system if this is the case
        + steps to reproduce
        + other useful details (e.g. screenshots, backtrace, strace)

It will help us a lot and it will increase the chance that the bug will be 
fixed.


I am sure that you will have more questions. Feel free to ask.

Enjoy OOo ;-)


-- 
Best Regards,

Petr Mladek
software developer
---------------------------------------------------------------------  
SUSE LINUX, s. r. o.                        e-mail: [EMAIL PROTECTED]
Lihovarská 1060/12                          tel: +420 284 028 952
190 00 Prague 9                             fax: +420 284 028 951
Czech Republic                              http://www.suse.cz/
--
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to