Closed Bug 14383 Opened 20 years ago Closed 18 years ago

deleteRegisterFile: Logging info shows registry info instead of disk info

Categories

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

All
Windows NT
defect

Tracking

(Not tracked)

VERIFIED WONTFIX

People

(Reporter: jimmykenlee, Assigned: dveditz)

Details

Build: 9/20/99 SeaMonkey build

1. From http://jimbob/trigger2.html, click drop-down button and select
   a_adddelcomp and trigger to install a file
2. From drop-down, then select a_delcomp and trigger

Install.StartInstall("Acceptance: a_adddelcomp", "acceptance", vi, 0);
err = Install.DeleteComponent(regName);
Install.LogComment("DeleteComponent returns = " + err);

RESULT:
The Install.log shows:
---------------------------------------------------------------------------
http://jimbob/jars/a_delcomp.jar     --     09/20/1999 15:14:44
---------------------------------------------------------------------------

     Acceptance: a_adddelcomp


     ** DeleteComponent returns = 0
     Item [1/1]	Deleting component: acceptance/a_adddelcomp

     Install completed successfully
     Finished Installation  09/20/1999 15:14:45

EXPECTED RESULT:
The install.log should not show "acceptance/a_adddelcomp", and instead it should
show the directory path to the file that is being deleted.  This is consistent
with the logging of the other functions.
Target Milestone: M15
I think we can live with this for beta 1.
Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall
Engine
set to M18
we can't delete a component, since we don't register 

bug meeting 3/20
Target Milestone: M15 → M18
Parcelling out Cathleen's bugs
Assignee: cathleen → dveditz
doesn't happen anymore.
Changing "DeleteComponent" to "deleteRegisterFile" in Summary to reflect new API 
naming.
Summary: DeleteComponent: Logging info shows registry info instead of disk info → deleteRegisterFile: Logging info shows registry info instead of disk info
Resetting target field for missed milestones
Target Milestone: M18 → ---
This feature has been removed, so we won't be fixing it.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WONTFIX
All gone.  Marking Verified!
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.