Labs/Jetpack/FlightDeck/Development Docs/SDK
|
THIS PAGE IS A WORKING DRAFT | 
|
| The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page. |
Jetpack SDK in FlightDeck
FlightDeck is using Jetpack SDK to create XPI from the source stored in the database.
Jetpack SDK is changing frequently. New versions might not be backwards compatible. To avoid compatibility errors FlightDeck should have many versions of SDK installed. It should also assign SDK version with the Add-on. Author of the Add-on should be able to change the version of the SDK.
Questions
- Should SDK be assigned to the Libraries? It makes sense that some Libraries may depend on a specific version.
- Should we make old docs available?
Currently
SDK is downloaded from bleeding edge Mercurial repository. It is placed in flightdeckenv/src/ and copied temporarily to /tmp/SDK-#addon_id-#revision_number/ for every XPI creation.
Proposition
How multiple SDK versions could be implemented.
Storage
- All versions will be placed in one directory which wouldn't be in VCS.
- Metadata will be stored in database
- Version name
- Subdirectory
Installation
A shell script which will take a tag (url ?) and version name as arguments. It will download the SDK and create the associated database entry.
UX
- Option 1*
jetpack-core Library (all Libraries) will have a drop-d