Normally siliconBrain projects are not intermixed into all the other software on you computer. So dir's like /usr/local/bin is untouched. Instead we create a /usr/<package> or /usr/local/<package> dir, where we put all things, which are relevant for that package. The package name includes the version, so that it is easy to run several versions of the same tool or application on the same computer. The siliconBrain generation tool, for example, will be installed into /usr/siliconBrain_0_0_0.
You can define a link /usr/siliconBrain pointing to the current version, so that, if you like, you can create references to a siliconBrain application, without considering the current version.
In packagePath/configuration you will find a setEnvironment, which
you can include somewhere. This file should have been included
(executed with a prefixing . ), in an environment, which uses
this siliconBrain application.
As a developer of a siliconBrain application, you will use
siliconBrain. So you will have something like
. /usr/siliconBrain/configuration/setEnvironment in your
~/.bash_profile. In that setEnvironment there is
packagePath/programs appended to the path, so that as a developer you can
use your own packages executables.
To be able to use in parallel two siliconBrain applications, which are
based on different versions of siliconBrain, all used lib's,
scripts or whatever will be installed into the applications dir.
The generated WEB is to be installed via ftp. The idea behind is an open source application developer, who works on a computer with changing IP address and having an Internet provider, which gives her some web space. Or a company developer who has to install the WEB on a special intranet server.