Welcome to [Rohan Pall]'s hints on how to use those '''sexy starkits!'''

----
''an abscence of magic, and no policy''

There is no presupposition about how your files are arranged other than that the top level main.tcl is to be interpreted at launch
[http://trixie.triqs.com/pipermail/starkit/2002-July/000089.html].

Unlike some other wrapping methods there isn't an enforced or assumed layout.

''The above is worth repeating, IMO.  All a starkit does, is contain a dir
hierarchy (even if just a flat one) which gets "mounted".  That mount
point happens to be the same spot as the starkit itself - in other words,
file "/path/to/my/starkit.kit" ends up becoming *dir* "/path/to/my/
starkit.kit/" while in use, with things like "/path/to/my/starkit.kit/
lib/" being a preferred place to put packages, because that's what
"starkit::startup" will set up for you, but it's all 100% wide open and
totally scripted/inspectable.''

----

'''writable writeable vfs'''

I packaged my mindweb app in a starkit.  All its data was also stored in the starkit.  I had read somewhere that by default starkits were writable (r/w) but this in fact has changed over summer 2002.
[http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&selm=jcw-147A42.16572031052002%40news1.xs4all.nl]
Now starkits are by default read-only (r/o) [http://trixie.triqs.com/pipermail/starkit/2002-July/000089.html], but the documentation is lagging behind that fact.

You make your starkit writable by doing it at wrap time:
  sdx wrap app.kit -writable

''2002-09-17 (September 17, 2002)'' sdx doesnt give any hints that this option exists when displaying help with
  sdx help wrap
but it does indeed exist! ;>


----
[Category TclKit]