557333 - Create 'cfx install' and 'cfx uninstall' targets

Status: RESOLVED WONTFIX

(Add-on SDK Graveyard :: General, enhancement)

Description

[Atul Varma [:atul]]

The Jetpack SDK was made to make it easier for folks to share code, so it'd be great to have basic package management commands that allow folks to share code really easily.

Among other benefits, this will allow folks who are creating Jetpack APIs to build them as packages rather than as patches against Jetpack SDK's trunk, making it very easy for developers to experiment with their library and provide feedback on its API (from both usability and technical quality perspectives). Among other things, this decouples the usability of an API from its QA.

Ultimately FlightDeck will probably be the primary "catalog" of Jetpack's CommonJS packages, but in the meantime we can use a static file, similar to what Narwhal did in its early stages of development (it may still do so now).

Additionally, 'cfx uninstall --all-third-party' or something similar could uninstall all third-party modules that didn't come with the SDK.

Comment 1

[Atul Varma [:atul]]

I believe Mikeal is working on a CouchDB-based package catalog, so I'm Cc'ing him on this. It could be nice for the default catalog to point to a Mozilla-hosted instance of his app. Or if that's too much trouble, we could just use a static JSON file.

Comment 2

[Myk Melez [:myk] [@mykmelez]]

The Add-on SDK is no longer a Mozilla Labs experiment and has become a big enough project to warrant its own Bugzilla product, so the "Add-on SDK" product has been created for it, and I am moving its bugs to that product.

To filter bugmail related to this change, filter on the word "looptid".

Comment 3

[Myk Melez [:myk] [@mykmelez]]

This seems pretty implementation-specific; we need to take a step back and figure out the broader package ecosystem plan before deciding on the specific features like this that can be tracked as bugs.