Closed Bug 1025823 Opened 10 years ago Closed 10 years ago

Approval to turn on ADB Helper autoinstall

Categories

(DevTools Graveyard :: WebIDE, defect)

x86_64
All
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: paul, Unassigned)

References

Details

The Firefox DevTools need to talk to Firefox OS. To do so, we need to use ADB (Android Debug Bridge): https://developer.android.com/tools/help/adb.html Installing and running ADB is not simple. We want to assist the user. Our solution is to package the ADB binaries in an addon, auto-install the addon when the user starts the Firefox OS devtools (these tools are part of Firefox Desktop), and run ADB programmatically. Then, the user will never need to worry or even hear about ADB. Some additional info: * The binaries stay in the Firefox profile directory (no conflict with any existing installation). * If the user uninstalls the ADB addon, it won't be re-installed automatically. * Afaik, ADB license is http://www.apache.org/licenses/LICENSE-2.0 * The size of the addon is < 500Kb We need a couple of approvals: 1) are we ok with auto-installing an addon when the Firefox OS devtools start? 2) are we allowed to distribute the ADB binaries in an addon?
Flags: needinfo?(gerv)
Yes, assuming you check and find that adb is indeed Apache-licensed (or has another open source license), then we are fine to distribute binaries in an add-on. We should make sure the users know where to find the addon's source, as a matter of politeness and good practice. Gerv
Flags: needinfo?(gerv)
Gavin, can you confirm you're ok with auto-installing this ADB addon when the AppManager is started for the first time?
Flags: needinfo?(gavin.sharp)
Assuming everything's OK from a licensing point of view, sure.
Flags: needinfo?(gavin.sharp)
We're adding licensing information in bug 1026910. Thank you both for your help.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: Firefox → DevTools
Product: DevTools → DevTools Graveyard
You need to log in before you can comment on or make changes to this bug.