Folks,
50 comments in 4 different JIRA tickets + 18 emails in a thread to
discuss the Android download changes does not scale.
This is my attempt at summarizing what has been agreed upon so far.
*Please* think twice before replying with just a "+1" that just makes
the thread bigger.
The main problem goal we want to achieve with the changes proposed so
far is to make the lives of our users easier: instead of downloading an
architecture-specific zip file that contains a bunch of APKs and two
tarballs, one would download a single zip file that contains what's
currently inside xwalk_app_template.tar.gz, with the difference that the
native_libs/ directory would contain libraries for both armeabi-v7a and
x86.
We'll then have something like this:
download.01.org/crosswalk/releases/
`-- android/
|-- beta/
| |-- arm/
| | |-- crosswalk-apks-4.5.6.7-arm.zip
| | |-- crosswalk-cordova-4.5.6.7-arm.zip
| | `-- crosswalk-test-apks-4.5.6.7-arm.zip
| |-- x86/
| | |-- crosswalk-apks-4.5.6.7-x86.zip
| | |-- crosswalk-cordova-4.5.6.7-x86.zip
| | `-- crosswalk-test-apks-4.5.6.7-x86.zip
| `-- crosswalk-4.5.6.7.zip
`-- canary/
|-- arm/
| |-- crosswalk-apks-5.6.7.8-arm.zip
| |-- crosswalk-cordova-5.6.7.8-arm.zip
| `-- crosswalk-test-apks-5.6.7.8-arm.zip
|-- x86/
| |-- crosswalk-apks-5.6.7.8-x86.zip
| |-- crosswalk-cordova-5.6.7.8-x86.zip
| `-- crosswalk-test-apks-5.6.7.8-x86.zip
`-- crosswalk-5.6.7.8.zip
* crosswalk-${VERSION}.zip is architecture-independent and, as
mentioned, is equivalent to what's currently called
xwalk_app_template.tar.gz with native libraries for ARM and x86.
* crosswalk-apks-${VERSION}-${ARCH}.zip will contain
XWalkAppHelloWorld.apk and XWalkRuntimeClientShell.apk (they're
currently inside apks/ in the crosswalk-${VERSION}-${ARCH}.zip we
ship).
* crosswalk-cordova-${VERSION}-${ARCH}.zip will contain what's currently
in the crosswalk-project/crosswalk-cordova-android.git repository +
the contents of xwalk_core_library.tar.gz inside
framework/xwalk_core_library.
* crosswalk-test-apks-${VERSION}-${ARCH}.zip will contain
XWalkCoreShell.apk, XWalkRuntimeClientShell.apk and
XWalkRuntimeShell.apk (they're currently inside apks/ in the
crosswalk-${VERSION}-${ARCH}.zip we ship).
The idea behind calling the architecture-independent archive "crosswalk"
is to make it simple for users to understand that they just need to grab
that archive to start using Crosswalk -- everything else is optional.
We'd then settle on packaging all archives as zip files for consistency.
Infozip's zip(1) will be used to create the zip archives, so I don't
expect any compatibility problems on Unix systems, and at least back in
my days Windows developers were more used to zip files than tarballs.
This would then be done to both the dev branch (ie. crosswalk master)
and the beta one.
_______________________________________________
Crosswalk-dev mailing list
[email protected]
https://lists.crosswalk-project.org/mailman/listinfo/crosswalk-dev
