Autoinstallation of bundles.
|Reported by:||cscott||Owned by:||mstone|
|Keywords:||update.1.1?||Cc:||cscott, marco, tomeu, Eben, walter|
|Deployments affected:||Action Needed:|
Bundles found with a magic name on a USB key should be automatically unpacked into /home.
This is to support the near-term use case of distributing large library content in a school deployment with limited network connectivity/bandwidth. Although in some cases it may be possible to have the kids individually click through the journal to install an .xol, if deployment team size/time is limited, a more efficient mechanism may be needed.
The size of the library bundle may prohibit installing via the journal (since that will result in a copy in the journal and another unpacked on disk).
Activities may be autoinstalled as static content in a library bundle (which may result in three copies of the activity ultimately ending up on the filesystem: one in the library, one in the journal, and one unpacked in /home) or directly (which raises some security issues, which may be partially addressed by activity isolation).
Target for this bug is update.1.1; we're assuming that we can't get a "better" solution in place in that timeframe.