We need more flexibility that a simple boolean "force" mode. The very first thing we need is a flag to indicate this file should be registered with XPCOM.

Moving non-dogfood bugs to M13

Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall Engine

moving to M14 due to dependencies.

Please elaborate for the neurally challenged PDT. Thank you.

Adding [NEED INFO] to Status Summary.

"Need Eng to Verify"

this is not required for Beta1 because the files (for now) already get registered via the -isntaller parameter when launching mozilla.exe for the first time. Reassigning to Don as well because he's already working on a similar bug that would fix this bug (per cathleen).

Dan, Can you give me an idea about how many "modes" we would want? So far there's 2: "force" and "register w/ xpcom". That would indicate a 2-bit bitfield.

Actually we're changing force to be the default. The force-related modes we need are "Install if newer" and "Install if same or newer". Then we need the component mode you mentioned, and possibly a "register chrome" mode. Or maybe some of those are separate methods. I think at this point we need only the force modes and the bitfield-ness of the thing, we can add other flags later. It should be a 32-bit integer, so we'll have plenty we can add later. (given the way JS works we may only get 30 or 31 bits to play with.)

Fixed. It's not actually a "bit field", it's really just an integer to which you can apply a mask to determine what has been set (e.g. a force mode, a special registration mode, a special handling mode, etc.)

Reassigning QA Contact to David.

An old stray bug. This was fixed long ago. It's working fine. Marking Verified!