[Starkit] possible sdx enhancements - create + fill

[Steve Landers]

On 24/01/2005, at 10:21 PM, Techentin, Robert W. wrote:

>> But on platforms that support symbolic linking, instead of
>> copying the
>> whatever.tcl script into
>> whatever.vfs/lib/app-whatever/whatever.tcl, it
>> creates a symbolic link. This matches the way I work on
>> Linux - the
>> real source file sitting next to whatever.vfs and a symbolic
>> link to it
>> from within the .vfs hierarchy.
>
> "sdx create" sounds great, but I'm not so sure about editing and 
> linking a
> file.  I don't think I would work that way.  Editing and moving
> "whatever.tcl" into the newly created VFS would be OK with me, because 
> it
> seems more like a transform.  But I don't usually create links between
> different copies of the same source file.  It's challenging enough to 
> keep
> all the CVS versioning intact.

Yes  - I don't think there is "one true way".

Having said that, the reason why I create the link is because I keep 
the original source (i.e the one next to the whatever.vfs) in CVS, but 
not the contents of the VFS directory.

Since CVS directories are ignored by "sdx wrap" I could do what you are 
suggesting, but then I'd either have t

This way during development I can edit using
	$ vi whatever.tcl

and invoke the application using
	$ tclkit whatever.vfs/main.tcl

But I'm just as happy to pull the link code out and call it "sdx link", 
so then I'd do
	$ sdx create whatever
	$ sdx link whatever
	$ sdx fille whatever

Steve