Configurable script path?

Discussion of Inner Space

Moderators: Lavish Software Team, Moderators

Post Reply
iluvseq
Non-Subscriber
Posts: 25
Joined: Sat Dec 18, 2004 8:15 pm

Configurable script path?

Post by iluvseq » Mon May 15, 2006 5:05 pm

I'd like to store my .iss files on a networked drive, and not in InnerSpace/Scripts.

I am unable to find anywhere to configure the locations of script files. Is this possible?

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Mon May 15, 2006 5:23 pm

Well, a couple little-known facts

1) As long as your networked drive is mapped to a drive letter, you can runscript g:/whatever/myscript.iss
2) Script locations can be stored in InnerSpace.xml under the "Scripts" set. By default you should see this if you open it up

Code: Select all

	<Set Name="Scripts">
		<Set Name="Example">
			<Setting Name="Filename">Example.iss</Setting>
			<Setting Name="Path">Scripts/Example</Setting>
			<Setting Name="Version">20051014</Setting>
		</Set>
	</Set>
You can add your own script under the Scripts heading like so:

Code: Select all

	<Set Name="Scripts">
		<Set Name="MyScript">
			<Setting Name="Filename">SomeScript.iss</Setting>
			<Setting Name="Path">g&#58;/whatever</Setting>
		</Set>
		<Set Name="Example">
			<Setting Name="Filename">Example.iss</Setting>
			<Setting Name="Path">Scripts/Example</Setting>
			<Setting Name="Version">20051014</Setting>
		</Set>
	</Set>
The version setting is not important -- it is for future packaging systems to help you auto-update (or install) scripts. Since your name is iluvseq I dont feel bad dropping a few linux terms: Sometime this year a default packaging system will come with Inner Space, likely with a UI, similar to stuff like apt, ports, etc. The only thing stopping this from being done already is having to either find or design an archiver that can be distributed in LavishScript module form (open source with compiled binaries or otherwise). Of course, I can easily create a system in an hour or two that is essentially a tarball + zlib compression, just with less features than tar, but it just hasnt been done at this point.

Anyway aside from my tangent there about a packaging system, script names found in the Scripts set are "registered scripts" that can be loaded by simply doing runscript <name>, regardless of the filename or location.

Code: Select all

runscript MyScript
will run g:/whatever/SomeScript.iss

iluvseq
Non-Subscriber
Posts: 25
Joined: Sat Dec 18, 2004 8:15 pm

Post by iluvseq » Mon May 15, 2006 6:45 pm

So there would need to be a setting under Scripts for each script I wanted to run from that location (unless I typed the full path in RunScript) ?

What about include files? Will they need the full path specified as well, or does InnerSpace look in the script's directory by default?

Lax
Owner
Posts: 6634
Joined: Fri Jun 18, 2004 6:08 pm

Post by Lax » Mon May 15, 2006 9:10 pm

So there would need to be a setting under Scripts for each script I wanted to run from that location (unless I typed the full path in RunScript) ?
Yes, for this method
What about include files? Will they need the full path specified as well, or does InnerSpace look in the script's directory by default?
LavishScript uses the script's directory by default

Post Reply