extract extensions

[jafeha]

the extensions have to get extracted to the right folder to get activated on startup.

for activated plugins place it here:

apps/<os>/thunderbird/distribution/exensions/<id>

for users to activate it, place it here:

apps/<os>/thunderbird/extensions/<id>
profile/extensions/<id>

what we have to check: are globally distributed extensions being updated or not? if they are, there is no reason, why we shouldn't use the distribution folder. if they aren't we have to dig deeper.

[jojoo-]

where do we get the id from?

[jafeha]

http://kb.mozillazine.org/Determine_extension_ID

[jafeha]

we will need some kind of id-extraction procedure similar to the mozilla script. for the moment i'd hard code the id into the extensions path variable.

[jafeha]

which is problematic: we don't the os where tb will run the first time, so we have to deploy the distribution folder of all tb versions with the extensions. so the path variable in config.ini would have to support wildcards, i have no idea if that works in that way:

path = %(tc_mountpoint)s/apps/*/thunderbird/distribution/extensions/

[jojoo-]

i'm not sure how we need to handle this.

glob.glob can produce a list of matching files, see the extract_dmg_mac for an example

[jafeha]

i have moved the extract code back to extract_files.py. the function for detemining the extension id still remains in utils.py

[jafeha]

got further with cb9b19e730. Extensions are working under linux.

[jafeha]

new there is a new function for extracting the id. furthermore, all extracted extensions seem to work. i close this issue.