Hi Christian, *,

Christian Lohmaier pisze:
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.

Actually, people were asking quite frequently about details regarding Windows build because they found one page about it but not another one in the wiki (there were several pages that were not linked to each other and it was really hard to find them). This is exactly what will be fixed by Per.

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)

This is true but if you're a new developer, you might be unaware of the fact that you can easily query IZ and find the patch already submitted by pjanik or others for such build problems.

I doubt that the new documentation will cause less questions.

Maybe there will be more questions because less people will be intimidated to build OOo and try their own patches.

And one more thing: OOo is mainly C++ but sometimes you might want to fix a small snippet of Java inside it, and for that you don't really have to know how to develop in C++. So there are cases when you don't have to be familiar with the usual C++ configuring stuff to submit a patch of some value.

Regards
Marcin

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

Reply via email to