Dennis E. Hamilton wrote:
1. one of tar.gz/.bz2 is probably the best choice. ...
That's a pragmatic solution, not a community-building one [;<). So be it.
Well, as we discussed so far, anybody willing to build on Windows has to
download tools capable of handling .tar.bz2 anyway, and someone who
can't expand a .tar.bz2 archive is frankly unlikely to succeed in the
(still quite tedious, as we are seeing) OpenOffice build process. So I
don't see risks to exclude developers by settling on .tar.bz2
2. ... tag/branch corresponding to the release, should provide the same files.
This is https://bz.apache.org/ooo/show_bug.cgi?id=126605
Differences are indeed minimal, but we'll fix it in 4.2.0.
The ext_sources are not code we want to ship anyway: the release
contains OpenOffice sources; for convenience we carry some external
sources in SVN, but we don't want to ship them. The "bootstrap" script
will download them from the official site or from repositories that are
under control of the project.
The 4.1.2 zip source was definitely not made from a native-Windows checkout.
They were all generated on a Mac.
Regards,
Andrea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org
