Please remove and blacklist pyxpcom from the archive
Bug #675587 reported by
Micah Gersten
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pyxpcom (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned |
Bug Description
Debian's version isn't compatible with our xulrunner. We're also not sure if we can support this across major Firefox/xulrunner updates at this time.
Changed in pyxpcom (Ubuntu): | |
importance: | Undecided → Wishlist |
status: | New → Confirmed |
To post a comment you must log in.
Just to be clear - the Debian package installs a binary component directly in to /usr/lib/ xulrunner/ components. On Ubuntu, this is a volatile directory, as it has a version number in it which changes between minor versions. This would mean we'd have to do a pyxpcom update every time we rolled out a Firefox security update.
In general, dropping random binaries in to the application directory is bad, and is strongly discouraged by Mozilla (this is why we have a components.list, to prevent these binaries from being loaded at run time and to discourage vendors from doing exactly this type of thing).
The only correct way to distribute the binary component provided by pyxpcom is to bundle it as an extension.