Hi Per, *, On Wed, Jul 15, 2009 at 10:43 PM, Per Eriksson<pereriks...@openoffice.org> wrote: > Christian Lohmaier skrev: >> On Wed, Jul 15, 2009 at 11:09 AM, Per >> Eriksson<pereriks...@openoffice.org> wrote: > > If a developer cannot find the building information it is probably because > there they can't find the information,
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. If you cannot find the "Building OpenOffice.org" wiki page, then I have no words to say. Those surely will not be able to find another wiki page. > or that there are too many documents, > including documents with wrong information. New documents are written > because they cannot edit the CVS documents etc. And please, please don't base your argumentation pro/agains a new guide on the situation as it was three or four years ago. The Building OpenOffice.org page exists in the wiki since 2006. > Of course this initiative includes: > - Updating links to the new content > - Provide redirects > - Promoting this guide on all the places where content is currently placed. For this, you don't need to write a new book > [...] > What I have identified is that we have an enormous amount of documents on > too many places. Yes. And now you're adding yet another place. >>> In this work various negative comments about building OpenOffice.org >>> being >>> impossible in the articles will be replaced by constructive tips for the >>> developer. >>> >> >> It never was complicated to build OOo on linux. Since aqua version is >> default, it is no longer complicated to build OOo on Mac OSX. The only >> problematic systems are Windows and other ports. >> > > What I am referring to is actually problems in the current documents, where > building is referred to as: > Complicated > Impossible > Ooo-build is much easier Yes, go-oo is freer, faster, better.. Sure thing. Of course go-oo folks write such propaganda. And probably all those complains are not about building OOo itself, but getting the right sources. What makes OOo slighly more complicated is its development structure. While still in cvs, you needed to use the OpenOffice2 alias (or OpenOffice2 and Extensions). THAT was chaos and complicated. People with problems didn't bother to checkout a milestone, but tried trunk, or did use the wrong alias and were getting incomplete/wrong sources. And of course then the complaint is "ah, this is all so complicated": But only complicated because the user didn't look for info before trying to build. Now with svn it is little easier, no aliases anymore, however still the Milestones. > [...] ciao Christian --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
