Closed Bug 16215 Opened 25 years ago Closed 25 years ago

[BETA]Move Install.fileXxx methods onto their own object

Categories

(Core Graveyard :: Installer: XPInstall Engine, defect, P3)

Product:
Core Graveyard
Component:
Installer: XPInstall Engine
Platform:
All
Other
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: dveditz, Assigned: dbragg)

Details

We should create a global File object in the install context to contain the
the current fileXxxx and dirXxxx methods from Install.  These still have to
know about the global "Install" object so actions can be queued, but the
namespace will be cleaner and easier to document.
Target Milestone: M11
Severity: normal → critical
Target Milestone: M11 → M12
Blocks: 18951
Summary: Move Install.fileXxx methods onto their own object → [BETA]Move Install.fileXxx methods onto their own object
Target Milestone: M12 → M13
Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall
Engine
Assignee: dveditz → dbragg
Status: ASSIGNED → NEW
dveditz reassigning to dbragg
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
fixed.  Now you can reference these methods from FileOp.<whatever> as well as
the Install.<whatever> format.
Reassigning QA Contact to David.
QA Contact: jimmylee → depstein
tested each Fileop method. Each one is supported in the "File" object, although 
there are several problems (submitted bugs for these).
Status: RESOLVED → VERIFIED
No longer blocks: 18951
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.