10129 - [feature] Version Registry: Package node not created after triggering jar file

Status: VERIFIED FIXED

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

Description

[Jimmy Lee]

Build: 7/16/99 SeaMonkey build

1. Backup or remove Netscape Registry from System Folder:Preferences for
   simplicity
2. Install 4.5, 4.61, or 4.7, launch and exit
3. SeaMonkey Macintosh does not have an installer yet, so just launch
   apprunner
4. Go to http://jimbob/jars/trigger2.html
5. Trigger any relative path jar like a_adddelcomp.jar
6. Exit and launch 4.x
7. Open http://slip/softupdate/BiggerRegToy.html and check the Version Registry
   for Communicator (or the node that corresponds to 4.x)

RESULT:
The Install.log indicates that the installation was successful.  The file
appears to be installed in the correct location.  There is no package node in
the Netscape Registry that corresponds to 5.0.  There is a registry setting,
"acceptance", from Communicator (or 4.x package node) that corresponds to the
the jar triggered from 5.0.

EXPECTED RESULT:
From Netscape Registry, a package node that corresponds to 5.0 with a registry
setting that corresponds to the triggered jar.  Components should not be
registered in other package nodes.  They should at least fail.

Comment 1

[Doug Turner (:dougt)]

I think that I have fixed this a few days a go.  Today's build should have the
fix in it.  Can you verify?

Comment 2

[Jimmy Lee]

Build 7/22/99

The problem still exists as described originally.

Comment 3

[leger]

Clearing Fixed resolution due to reopen.

Comment 4

[Daniel Veditz [:dveditz]]

Hard to believe this is only on Macintosh

Comment 5

[leger]

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

Comment 6

[Cathleen]

we think this is fixed.  Jimmy, please help verify.  ~ thanks!

Comment 7

[Jimmy Lee]

Build 2000-03-21-05-M15-nb1b (Mac)

Currently, we register only the package node.  This has been working for a long 
time now.  Marking Verified!