I have run into bug in the starkit::startup procedure. This
procedure should always return a key word that indicates the
type of object that is being started (e.g. unwrapped, starkit,
starpack, ...etc.). The bug occurs when a starpack is run on a
solaris system but not on hpux systems. I don't have have
information on other platforms.
Here is what I have found.
1) create a test file that contains the following
----- file start -----
#!/bin/sh
# the next line restarts this file using a tcl shell \
exec tclkit "$0" -- ${1+"$@"}
package require starkit
puts "##([starkit::startup])"
----- file end -----
2) convert test file to starpack named "test"
3) create the following directory /disks/proj1 (which may require
root access)
4) put the starpack (test) in the /disks/proj1 directory
3) create a soft link (/proj1) that points to the /disks/proj1
directory (this may alos require root access)
/proj1 -> /disks/proj1
6) now execute the starpack using
/disks/proj1/test
and you will get
##(starpack)
5) but when you execute the starpack using
/proj1/test
and you will get
##(unwrapped)
which is a bug.
Regards,
Tom Krehbiel
P.S. I don't have control of the way systems are configured
where my code is installed so don't blame me for the link. This
bug was reported by a user who doesn't have root access.

Soft links, i.e. symlinks, and VFS don't seem to go together well yet. I'm
not quite sure
where this can be fixed, it seems to be a difference in the way files are opened
at first
and then later re-opened by MK and VFS.