283352 - Make new flat chrome manifests usable by extensions

Status: RESOLVED FIXED

(Toolkit :: Startup and Profile System, defect)

Description

[Benjamin Smedberg]

The new flat chrome manifests are currently not usable by extensions because the
manifest is overwritten while doing compatibility. This patch makes sure that we
upgrade/delete/manage the chrome.manifest files in an extension properly such
that extensions can include a chrome.manifest in the root of their XPI.

Comment 1

[Benjamin Smedberg]

Attachment: Delete/extract/overwrite chrome.manifest correctly

Comment 2

[Mike Shaver (:shaver -- probably not reading bugmail closely)]

Comment on attachment 175345 [details] [diff] [review]
Delete/extract/overwrite chrome.manifest correctly

I would like a more descriptive comment than "doing the RDF thing", perhaps
"generating one from contents.rdf data", but with that I am pleased to
r=shaver.

Comment 3

[Benjamin Smedberg]

Fixed on trunk. Updated documentation is at
http://www.mozilla.org/projects/firefox/extensions/packaging/extensions.html

I could use help spreading the word about this checkin amongst extension
authors. My blog is down from having moved websites and not configured the new
one yet.

Comment 4

[Bradley Chapman (not reading bugmail, still gone but not forever)]

I'll make a thread on MozillaZine and get a mod to sticky it. How's that?

Comment 5

[Bradley Chapman (not reading bugmail, still gone but not forever)]

http://forums.mozillazine.org/viewtopic.php?t=228092 is the thread I created.

Comment 6

[Alex Bishop]

> I could use help spreading the word about this checkin amongst extension
> authors. My blog is down from having moved websites and not configured the new
> one yet.

You can have a front page MozillaZine article if you like. Just write something
and send it via http://www.mozillazine.org/submit/ and I'll put it up.