Can't login now (and won't be able to for a while), so putting some comments
here:

I think there definitely should be examples, 1-2 for every place where
variants are supposed to occur. If that's a 'one size fits all' guide (both
experienced guys and building newbies), than '<something>' convention might
be somewhat confusing. I seem to remember MS internal help uses another kind
of braces for such stuff.

Do not remove the mention(s) of SVN repository completely - external sources
might exist still pointing to it. Just move it to a subpoint, with a
suitable comment(s). (Is it going to be phased out? Is it synchronised? Is
it read-only? What stuff does it hold?)

Mention unowinreg.dll.

Is the 'clean' procedure described in the 'Incompatible Build' actually
tested and 'official' way to do 'make clean'? I can't check right now, but
like 2-3 weeks ago I had problems.

The Scons materiel in earlier topics posted by Damjan Jovanovic might be
mentioned, too.



--
Sent from: http://openoffice.2283327.n4.nabble.com/Development-f2916443.html

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Reply via email to