Migrate SeaMonkey installer from xpinstall to toolkit.

RESOLVED INVALID

Status

RESOLVED INVALID
13 years ago
12 years ago

People

(Reporter: standard8, Assigned: standard8)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

As part of the SeaMonkey transition to toolkit, the installer should also use the new toolkit one.

I propose that the new parts of the installer will reside as follows:

/suite/installer - Main installer files (with unix and win directories initially, maybe more later)
/suite/locales/en-US/installer - locale information (specific for SeaMonkey installer)
/suite/branding/content - image files (equivalent of header.png and watermark.png as per http://lxr.mozilla.org/seamonkey/source/browser/installer/unix/ )

As I expect we want to use xpinstall until we are ready to flick the switch, then my current plan is to do as much as possible whilst leaving the *.jst files and packager (list of packages) files under /xpinstall/ just pointing the installer files at them.

Comments welcome.
Discussing this with ajschult on irc, he says that the linux toolkit installer has many problems and is missing fixes that the xpinstall version has. Therefore for the time being at least we should stay with the linux xpinstall installer and update it for l10n issues where necessary.

However, moving to the windows toolkit installer will be a gain for us (sort out gre problems etc), so I'll see what I can do to aid moving that.

Comment 2

13 years ago
Actually, we're ditching the current toolit installer; I don't recommend switching to it now. http://wiki.mozilla.org/User:Beltzner/Specification_of_Stub_Installer_User_Interface

Updated

13 years ago
QA Contact: bugzilla → general

Comment 3

12 years ago
The toolkit installer is now gone.  Work to use the NSIS installer is happening in bug 351917... is this INVALID now?
(In reply to comment #3)
> The toolkit installer is now gone.  Work to use the NSIS installer is happening
> in bug 351917... is this INVALID now?
> 

Assuming the linux toolkit installer has now also gone (or is planning to be; one of which I believe is the case), then yes, this should be invalid - I'll mark it as such, so please reopen if I'm wrong.
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.