159021 - rshell.ini in config workspace dir doesn't get copied to output dir when build

Status: RESOLVED WONTFIX

(CCK Graveyard :: CCK-Wizard, defect)

Description

[Jimmy Uen]

Instead the Tool builds the rshell.ini from part1.ini and part2.ini in the
installed directory.

We supply documentation to modify rshell.ini. When a user modify the rshell.ini
in the config workspace directory and build the installer. He/She expects that
the rshell.ini gets pick up in the installer which doesn't. Now the workaround
for this is that he/she can copy initial modified rshell.ini from the workspace
directory to the output directory.

The Tool should not be building rshell.ini since it's already available in the
workspace directory. Since workspace directory is the place where we recommend
our user to make all their customization, we should just copy rshell.ini from
the workspace directory. Also this way we can conserve space by removing
obsolete part1.ini and part2.ini both in root install directory and
workspace\autorun\shell.

Comment 1

[Jimmy Uen]

marking docrtm+

We need to release note this for CCK 7.0 RTM.

Comment 2

[blee]

Unless the doc is changed, it suggests CCK users edit Rshell.ini file in 
Output(\Shell\nsetup32\) dir of the custom bld installer. This may seem 
somewhat inconsistent in that most other custom files of users are to be drawn 
from Workspace dir. Then again, this was offered as an additional (advanced) 
customization feature.

Comment 3

[Mike Kaply [:mkaply]]

Old CCK.