Closed
Bug 6719
Opened 25 years ago
Closed 25 years ago
Install.SetPackageFolder() needs to be implemented.
Categories
(Core Graveyard :: Installer: XPInstall Engine, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M7
People
(Reporter: ssu0262, Assigned: cathleennscp)
References
Details
It currently simply returns NS_OK.
Comment 1•25 years ago
|
||
From dveditz email:
This is defined in the documents on warp, the manual doesn't explain
this parameter (descriptions of the overloading is pretty poor).
For forms that don't take a folder object it will use the "package
folder" if one is set, otherwise it's an error. The "package folder"
should be an internal variable of the nsInstall object (which probably
isn't there since SetPackageFolder() is not implemented).
If a package folder is set with SetPackageFolder() then it will be saved
in the registry, and can be used in these overloaded forms. If a default
package folder is found in the registry then it can be used in
overloaded forms without calling SetPackageFolder() -- but that would be
pretty ballsy to do in an install.
Instead, I would recommend something more like
fpackage = Install.GetComponentFolder("mypackage");
if ( fpackage == null ) {
fpackage = askuserforfolder();
Install.SetPackageFolder(fpackage);
}
(Instead of asking the user you could simply GetFolder() some known
place where you want to do the install.)
In practice I suspect most installers simply stomp themselves into
specific directories and don't bother to check to see if a previous
version was installed somewhere else. Or if they check they do so via
the windows registry, which might be expected to stick around better
than info in the netscape registry.
added a task into the schedule, will figure out who can own this task.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
I took the liberty to fix this since I fixed the related bug
http://bugzilla.mozilla.org/show_bug.cgi?id=6612
Look for the fix in the next build.
*** Bug 6739 has been marked as a duplicate of this bug. ***
Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall
Engine
Updated•9 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•