Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Starkit from a starkit

5 views
Skip to first unread message

iu2

unread,
Nov 17, 2009, 2:20:45 AM11/17/09
to
Hi all,

I tried to include wikit.kit inside my starkit. The tcl wiki explains
how to do that by unwrapping wikit.kit and copying 3 folders to my
starkit vfs. This works fine.
What I'm trying to do instead is including wikit.kit itself in the
starkit and source is, like this:

srouce [file join [file dirname [info script]] wikit.kit]
catch {package require Wikit} ;# wikit version error
Wikit::init myfile.tkd

When I do this I get the error:

file open filed
while executing
mk::file open mk4vfs1 c:/..../wikit.kit -readonly
...

I use tclkit 8.5. How can this be solved?
Also, given any other starkit, what is the way to re-use it in my own
starkit?

Thanks

Donald G Porter

unread,
Nov 17, 2009, 9:07:17 AM11/17/09
to
iu2 wrote:
> I tried to include wikit.kit inside my starkit. The tcl wiki explains
> how to do that by unwrapping wikit.kit and copying 3 folders to my
> starkit vfs. This works fine.
> What I'm trying to do instead is including wikit.kit itself in the
> starkit and source is, like this:
>
> srouce [file join [file dirname [info script]] wikit.kit]
> catch {package require Wikit} ;# wikit version error
> Wikit::init myfile.tkd
>
> When I do this I get the error:
>
> file open filed
> while executing
> mk::file open mk4vfs1 c:/..../wikit.kit -readonly
> ...
>
> I use tclkit 8.5. How can this be solved?

You can't. It is a limitation of the mkfs filesystem driver that
it does not support nested archive files. [mk::file open] can
only operate on archive path names that are from [file system] => native.

> Also, given any other starkit, what is the way to re-use it in my own
> starkit?

You gave the working advice above, unpack the contents and add them to
the main archive.

MSEdit

unread,
Nov 17, 2009, 12:22:34 PM11/17/09
to

Another possibility is to overload the source command to copy the kit
out to a TMP location and mount it from there before sourceing the
contents.

Could this be a tip for Starpacks ?

It is probably easier to unpack the kit and copy the files into your
VFS tree.

Martyn

Donald G Porter

unread,
Nov 17, 2009, 12:27:24 PM11/17/09
to
MSEdit wrote:
> Another possibility is to overload the source command to copy the kit
> out to a TMP location and mount it from there before sourceing the
> contents.

I think you would want to overwrite [mk::file open] instead of [source].

DGP

MSEdit

unread,
Nov 18, 2009, 7:55:18 AM11/18/09
to
On Nov 17, 6:27 pm, Donald G Porter <d...@nist.gov> wrote:
> I think you would want to overwrite [mk::file open] instead of [source].
>
> DGP

That would work as well but source knows when the file has been used
and can unmount and delete the TMP file.

Martyn

0 new messages