versioning, epubReadingSystem, grunt build task, git-describe

[danielweck]

This applies to all "launcher" repositories, of which the Readium cloud reader / Chrome extension is one.
Currently, the build script works, but the navigator.epubReadingSystem runtime object is not populated with the versioning information.

[danielweck]

See @dmitrym0 's work:

https://github.com/dmitrym0/readium-shared-js/commits/develop
(Note all of the "Auto version update" commits)

dmitrym0/webhook-deployer@09e5edc#commitcomment-6981345

[danielweck]

Task: move to dedicated feature branch
https://github.com/readium/readium-js-viewer/blob/develop/update-version.sh
https://github.com/readium/readium-js-viewer/blob/develop/readium-module.json
https://github.com/readium/readium-js-viewer/blob/develop/epubReadingSystem.json
etc.

[danielweck]

Moved to feature branch:

https://github.com/readium/readium-js-viewer/tree/feature/version

[danielweck]

See also submodules (only additions "readium-module.json" and "update-version.sh"):
https://github.com/readium/readium-js/tree/feature/version
https://github.com/readium/readium-shared-js/tree/feature/version

[danielweck]

Note that the grunt shell invoke is asynchronous, so unlike git-describe it doesn't actually work properly right now.
WIP!
https://github.com/readium/readium-js-viewer/blob/feature/version/grunt/epubReadingSystem_processModules.js#L37

[danielweck]

@ryanackley thank you very much, this looks great!

I added a separate issue for v1+ (populate epubReadingSystem with detailed version info, similar to my original feature branch):
readium/readium-shared-js#104

[danielweck]

@ryanackley here is a follow-up to this, now populating the navigator.epubReadingSystem object: #222

The aforementioned Pull Request includes a new EPUB (in epub_library.json), to display/dump the augmented navigator.epubReadingSystem object (which now contains an additional "readium" field).

Note: this is a simpler design compared to my original "version" feature branch (linked a few comments above), as this is not using a generic hierarchical data structure to describe submodule dependencies (the 3 repository references are hard-coded, piggy-backing on the existing "versioning" code that looks at readium-js-viewer, readium-js, and readium-shared-js). Furthermore, there is no build-time "git-describe" to automatically extract the nearest tag/release name (if needed, this can be obtained "after the fact" from the provided git commit SHA using the command line 'git name-rev --tags --name-only SHA').

I'd appreciate your feedback, thanks!