Closed
Bug 305361
Opened 19 years ago
Closed 19 years ago
install-global-extension and install-global-theme work inconsistently
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: robert.strong.bugs, Assigned: robert.strong.bugs)
Details
(Keywords: fixed1.8)
Attachments
(1 file)
3.09 KB,
patch
|
benjamin
:
review+
asa
:
approval1.8b4+
|
Details | Diff | Splinter Review |
The functions used by install-global-extension and install-global-theme use the
same functions that are used during an interactive install and often provide
inconsistent results... often the item is staged which will require an
interactive session with rights to the app location to complete the install. For
1.5 these command line flags should expand the xpi/jar into the app extensions
directory or they should be removed entirely. Patch coming up.
Assignee | ||
Comment 1•19 years ago
|
||
This extracts the extension or theme into the app extensions dir and then
upgrades its chrome. This has essentially the same end result as extracting an
extension or theme into the app extensions dir and then launching once to
upgrade the chrome if necessary so other users on the system can use the
extension or theme.
These command line args are rather broken currently on the branch and I think
this should be considered for 1.8b4. One example
if (globalTheme) {
- var file = commandLine.resolveFile(globalExtension);
Attachment #193317 -
Flags: review?(benjamin)
Assignee | ||
Updated•19 years ago
|
Flags: blocking1.8b4?
Updated•19 years ago
|
Attachment #193317 -
Flags: review?(benjamin)
Attachment #193317 -
Flags: review+
Attachment #193317 -
Flags: approval1.8b4?
Comment 2•19 years ago
|
||
We should either take this (rather simple) patch, or remove the "-install-*"
flags completely.
Flags: blocking1.8b4? → blocking1.8b4+
Assignee | ||
Comment 3•19 years ago
|
||
Fixed on trunk - leaving open for possible 1.8b4 approval
Updated•19 years ago
|
Attachment #193317 -
Flags: approval1.8b4? → approval1.8b4+
Assignee | ||
Comment 4•19 years ago
|
||
Fixed on trunk and MOZILLA_1_8_BRANCH
Updated•17 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•