Christian Lohmaier <cloph <at> openoffice.org> writes: > My problem is that everyone is eager to start new projects, new > efforts instead of improviing what is there already. Cleaning up the docs _is_ improving what is already there.
> My problem is that if you really feel the need of simplifying the > build, then don't do it by adding instructions, but by actually making > the build itself simpler. Is a different scope and there are different skillsets needed for both tasks. And both efforts can produce better results. > No. I did compile OOo myself for the first time in the past as well. > At that time, I just did read the instructions and off it went. I did > look for info. I didn't assume I know already. Well, I you look at the current wikipages, it reads like its written by an ADHS-impaired kid: Lots of "You might want to ...", "You might need to ..." etc. with workarounds for problems that are likely long gone. Quoting the Zen of Python: "There should be one-- and preferably only one --obvious way to do it." The docs currently provide too many options without noting the one that is the: - most useful - most robust - best documented, updated and supported > If configure prints "get <file> from <URL> or use mingw" and people > still complain about not being able to tell where to get <file>, that > sepaks for itself. For example, in that particular case I am still wondering, why the <URL> that configure barfs out isnt a direct one (that is wget-able), but one to an directory where one finds the link to the real unowinreg.dll. Thats just unneeded hassle. > Probably that's another part of the problem I have. This makes it > sound like there wouldn't be any documenation for new builders at all. > That's just not the case. Actually, outdated documentation is much worse than no documentation. Have Fun, Bjoern --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
