Closed Bug 6116 Opened 25 years ago Closed 25 years ago

AddSubcomponent: Cannot add relative path to target name

Categories

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

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jimmykenlee, Assigned: dougt)

Details

Build: 4/28/99 Engineering build 1. Trigger http://jimbob/jars/ascnesttgt.jar to add a component 2. A subdirectory, ascnesttgt, is created from the Program directory using GetFolder 3. The following call is made to add a component: Install.AddSubcomponent("ASCNestTgtcomp", "1.2.3.4", jarSrc, f, "ASCNestTgt1/ASCNestTgt2/"+jarSrc, true); RESULT: The Install.log reveals that the jar is started, but not finished. The log does not show any abort of the installation. As expected, the subdirectory, ascnesttgt, is created from Program. The component does not get installed. EXPECTED RESULT: The log shows successful installation. The component gets installed to Program/ascnesttgt/ascnesttgt1/ascnesttgt2/smrtupdt.txt NOTE: This bug was previously communicated by email. It should not be tracked by this record. This is a regression jar from 4.5.
QA Contact: 4395 → 4138
Changing QA Contact from Grace to Jimmy.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Fixed. nsInstallFile was not created the nested directories properly. The jar install a file into BIN\ascnesttgt\ASCNestTgt1\ASCNestTgt2\ named smrtupdt.txt
Status: RESOLVED → VERIFIED
Build 6/1/99 Windows Looking good. Subdirectories get created as expected and component is added.
Bulk move of XPInstall (component to be deleted) bugs to Installer: XPInstall Engine
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.