Closed
Bug 7868
Opened 25 years ago
Closed 25 years ago
CCK needs complete jar contents manifest and dependencies
Categories
(SeaMonkey :: Installer, defect, P3)
Tracking
(Not tracked)
VERIFIED
FIXED
M15
People
(Reporter: selmer, Assigned: cathleennscp)
References
Details
We need to know what's in each jar in order to build install builder for 5.0. If we represent inter-jar dependency data, then we need to know how that's done so we can show it in the install builder UI. One problem dependency data solves is avoiding a build that won't install because it's missing required components.
We've got a manifest file list for XPI files, and it will be checked into the tree. We will also be putting in XPI files dependency tracking support in the InstallWizard. We need to make sure the dependencies are exposed for CCK, onece it's implemented. dependency tracking bug for win Wizard: 11215 dependency tracking bug for mac Wizard: 11216 Adding these bugs into this bug dependency list. Reassign to Sean and cc Samir.
minifest file for window is checked in under mozilla/xpinstall/manifest-win
Dependencies will be done by m10 on the Windows platform. Samir, how is it looking on the Mac platform?
Assignee: ssu → cathleen
Status: ASSIGNED → NEW
Target Milestone: M10 → M15
Bulk changing all JAR Installation component bugs to Installer: XPI Packages
xpi manifest files are under mozilla/xpinstall/packager/package-[PLATFORM] ns/xpinstall/packager/package-[PLATFORM] ns will take precedence over mozilla where files overlap.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Browser → Seamonkey
Component: Installer: XPI Packages → Installer
QA Contact: agracebush → general
You need to log in
before you can comment on or make changes to this bug.
Description
•