Wei Zhang wrote:

> Dear OOo developers,
> 
> I am doing some investigation on the concurrency bug detection, and I am
> studying some "old concurrency bugs". And I feel OpenOffice has very
> detailed bug report and thus make a very good candidate for the study. For
> example, I am looking at this bug :
> 
> http://www.openoffice.org/issues/show_bug.cgi?id=44627
> 
> It is said that the version is 680m79 and Target milestone:OOo 2.0.2.
> 
> However, I am not sure how to get the source code of this or how to check it
> out from CVS or SVN. And it would be great if there is some document about
> how to build this "very old" OOo.
> 
> I did manage to download some source code tarball from some unofficial OOo
> website. One of the tarballs is labeled as  OOo_2.0.0_src.tar.gz and the
> other tarball that is labeled as OOo_2.0.1_src.tar.gz. I am not sure if I
> have downloaded the right one for the bug I need to study in the first
> place. And When I was trying to build the whole thing according to
> http://tools.openoffice.org/dev_docs/build_linux.html, I came across various
> issues with the JDK version and ANT version. After I googled around, I am
> using JDK 1.4.2 and ANT 1.6.2. There are still some other issues that I find
> pretty hard to resolve even after googling.
> 
> So I am trying to ask this: (1) is there a way that I can check out the
> legacy code, furthermore,  from the bug report how can I tell which tag or
> branch of the source code I should download/checkout (2) is there any
> document regarding what the system requirement for a particular build, such
> like the java version, c/c++ version etc (3) once I have retrieved the
> source code, is it true that I can always just follow
> http://tools.openoffice.org/dev_docs/build_linux.html to build the software

(1) Yes, there is. You can check the sources for all 2.x revisions out
from cvs. In your case (SRC680_m79) it would be:

cvs -d :pserver:[email protected]:/cvs co -r
SRC680_m79 OpenOffice2

You can check out the source for any tag you find in the sources.
SRC680_m79 was a development milestone, the release of 2.0.2 would be
OpenOffice_2_0_2

(2) I'm not aware of a comprehensive descriptions of build requirements
for all possible OOo revisions. I think the product requirements can
give a hint.

(3) The build instructions on tools.ooo are a little bit outdated, maybe
that makes them good for old revisions. :-) In general the instructions
in the wiki are preferable (the start page has a link in the
development section where you can start).

Regards,
Mathias

-- 
Mathias Bauer (mba) - Project Lead OpenOffice.org Writer
OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS
Please don't reply to "[email protected]".
I use it for the OOo lists and only rarely read other mails sent to it.


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to