[EMAIL PROTECTED], 03-05-2007 01:20:
The source is the same but the builds are different. For
example sun builds with crash reporter enabled, on-line
update enabled, and Quickstart disabled. There may be other
differences? So the builder might not bear the blame. There
was a bug in on-line update that could not be seen unless it
was disabled ;)
It doesn't matter a lot.
There are two possibilities:
- it's a bug on the compilation environment, on the build, package or
upload process
- it's a bug on the product.
These bugs should be reported and the place for this is Issue Tracker.
If you find a bug on the product on a own build, it still being an OOo
issue.
There are a lot of cases that depend on the compilation environment and
configuration: if cairo enabled or not, if it was built with system
mozilla, if it's binfilter enabled, if it's online update enabled, the
jdk used (assuming it's an issue on how OOo threats it, not a bug on the
jdk itself)...
If you do your own build of OOo downloading from the OOo repositories
and without any patch applied, you should use Issue Tracker.
The worse may happen is someone to invalidate your issue because you did
something wrong (of course you should check it twice, but assume you're
not a master on every subject).
Since Sun likes to use gcc 3.3 for instance, it would be hard to the
people who likes building with gcc 4.x, if they couldn't use Issue
Tracker :P.
If the issue is with some of the linux.cz packages and
does not happen on the official one, you should put it
clear on the description and maybe add pj (@ooo) to the
CC field ;).
I hope he doesn't mind, you probably meant pjanik ;)
Yeah pjanik, sorry.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
