Provides tarball in download

Thank you for asking but we don't have a plan to provide source tarballs under 
the current circumstances.

There are some lessons learned from our source tarballs that were previously 
provided in the download page.  First of all, our source tarballs were not well 
maintained in fact, and such poorly maintained tarballs even made people 
confused.  Issue 59 and Issue 197 are good examples.  More confusingly, you 
cannot build Mozc for Windows, NaCl (ChromiumOS), and Android only with those 
tarballs.  You still need to check out some additional sources as documented in 
the instruction page.  Apparently our source tarballs were not well maintained.

If you need source tarballs, my suggestion is to make your own mechanism to 
generate tarball for your own use.  If you want to share such source tarballs 
with others, don't forget that Mozc supports several platforms and your tarball 
might be insufficient for other platforms.  So the file name should be named 
like mozc-linux-1.15.1829.102.tar.bz2 rather than mozc-1.15.1829.102.tar.bz2 so 
as not to get people confused if you support only one particular platform with 
your tarball.

Just FYI, the gclient command that we are currently using to check out Mozc 
source code is also developed and maintained as a part of Chromium OSS project. 
 So theoretically you should be able to establish your own automated mechanism 
to generate tarball whenever Mozc repository is updated.
http://dev.chromium.org/developers/how-tos/depottools#TOC-DEPS-file
https://code.google.com/p/mozc/source/browse/trunk/src/DEPS
https://code.google.com/p/chromium/codesearch#chromium/tools/depot_tools/gclient
.py

Hope this helps and thank you for your understanding.

Original comment by yukawa@google.com on 6 Jul 2014 at 1:05

Changed state: WontFix
Added labels: Type-Task, OpSys-All
Removed labels: Type-Defect

axsann / mozc

Provides tarball in download #237