Hi Jörg, Jörg Jahnke wrote: > it looks like no one really uses the Solver tarballs. Therefore I > suggest we simply drop the creation of them.
For the purpose of providing patch files to customers who have installed an official build delivered by the RE and could not wait for a bug fixing upcoming official build, solver tar ball would be quite useful and reliable. Here is a documentation, not have been maintained though, describing how to utilize a solver tar ball. http://wiki.services.openoffice.org/wiki/Development_Environment_with_solver Meanwhile, I can agree with the idea dropping a creation of solver tar balls to avoid unnecessary costs. In such a case, it would be helpful if a little bit more detailed information on the build tools and environment became available. For instance, the Wiki page could be updated for 3.x. http://wiki.services.openoffice.org/wiki/Compiler_versions_used_by_port_maintainers_and_release_engineers What I have been doing for customers is: - A customer installs an official build built by the RE. - The customer suffers from existing bugs and/or needs extra features. - I am trying to fix bugs and/or implementing some additional features and then providing the customer with a small set of .dll/.so files and concurrently submitting patch files to the development team. Primary customers whom I have a contract with currently use 2.4.x, not 3.0 because of the instability and regressions around East Asian language specific functionality in 3.0. However, the demand of handling with OOXML file format is rising. So, they would need to proceed to 3.x. The Wiki page mentions about 3.0 saying "plan to migrate ..." It could be said that information on 3.x was not adequate. Additional information on 3.x would be greatly helpful. In sum, if we were able to locally set up a build environment that was compatible to the one used by the RE, solver tar balls would not be mandatory, I think. Regards, Tora --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
