Hello,
Here is how far I've come so far.
Several pages' content have now been moved to these 7 pages:
http://wiki.services.openoffice.org/wiki/Development/OpenOffice.org_Building_Guide
They originate from various places (which can be hard to find), including:
http://tools.openoffice.org/background.html
http://tools.openoffice.org/dev_docs/build_linux.html
http://tools.openoffice.org/dev_docs/build_solaris.html
http://tools.openoffice.org/dev_docs/build_windows_tcsh.html
http://wiki.services.openoffice.org/wiki/Building_OpenOffice.org
http://wiki.services.openoffice.org/wiki/Windows
http://wiki.services.openoffice.org/wiki/Building_OOo_with_Cygwin_on_Windows
http://wiki.services.openoffice.org/wiki/Build_Requirements
http://wiki.services.openoffice.org/wiki/Build_Linux_Requirements
http://wiki.services.openoffice.org/wiki/Build_Windows_Requirements
http://wiki.services.openoffice.org/wiki/Build_Solaris_Requirements
We are currently *saving* 4 pages, and it will surely increase to more.
Some wiki pages already redirect to this new content. The plan is to
redirect all the pages, including the tools html pages, each to the
corresponding new documents.
It will surely be easier for us to update the pages when they are placed
more together.
It will also be easier to spot irragularities as the instructions are
closer to eachother.
I have not moved any content for Mac, and I will not do.
What I need help with:
** Go through the Windows pages and do any updating that might be needed
to the new document. We want all the correct information to be in the
new document.
http://wiki.services.openoffice.org/wiki/Building_OOo_with_Cygwin_on_Windows
http://wiki.services.openoffice.org/wiki/Building_OpenOffice.org
http://wiki.services.openoffice.org/wiki/Windows
http://tools.openoffice.org/dev_docs/build_windows_tcsh.html
E.g. the section about getting the source is already covered by this
topic in the guide.
** Design fixes to the new documents, there are still some structure
stuff to improve.
Per
Juergen Schmidt skrev:
Hi Christian,
i really don't understand what your problem is. Maybe you missed the
goal of Per's work, it is simply the consolidation of several
different pages into one new place, put some structure on it and
extend or improve it where necessary. From my point of view structure
is always good and the documentation project did a good job here. So
why not using the same technique in other places. Call it guide, book
or whatever. In the end you don't have to read it all, you will be
guide to the pages you need.
And i think you look on it with the wrong glasses. You are very
familiar with all this stuff and it's clear for you as well as for
others. Great you can read configure but many others not. But they
maybe want to build OOo on their own because they can C++. And they
are maybe able to fix some issues, are able to create patches (with
the right instruction), etc. etc.
The work Per is doing is not for the developers we already have it is
probably more for new ones. We should support this effort with the
knowledge we have and make it a valuable resource for new developers.
The only place we have to maintain for future changes, improvements in
this area.
Juergen
Christian Lohmaier wrote:
Hi Marcin, *,
2009/7/16 Marcin Miłkowski <[email protected]>:
Christian Lohmaier pisze:
I still disagree. Basically /all/ of the questions asken on IRC about
building OOo were because people are unable to read configure or
because they don't use vanilla build system. Most of those didn't
bother to read any instructions, didn't look for instructions.
I could reply that probably using IRC is eating their brains ;) as most
questions asked at dev seem to be quite different.
Those questions will not be answered by a building OOo for newbies
guide.
The one I remember fall into the not using vanilla OOo/not taking
advice given category.
The other ones were build breakers are introduced (already built
successfully in the past, newer milestone breaks). System components
change in a incompatible way. Nothing that could be covered in a
simple guide. (but rather are bugs in the code)
[...] Linux build was strangely broken).
Those even less.
To get this straight:
I'm /not/ against consolidating the pages, au contraire, I support
getting rid of old pages.
But:
I am against yet another place (instead of reusing the existing pages)
I am against the structure as it appears now
I doubt that the new documentation will cause less questions.
I'm speaking for myself only, and of course don't tell anybody to stop
with the efforts.
ciao
Christian
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]