The installer of applications of child repositories using sight plus another repository should now be functional again.
The main fix is to give a relocatable path to the executable, like
sightrun. Now we locate it relative to the launcher script location.
Similarly, extra modules were given with absolute paths. We now use a relative path. We needed to modify Sight to accept relative paths, which are interpreted as relative to the executable path (and not the current directory, which is too fragile).
Last, when fixing this, we discovered that the extra modules were installed in the sight directory. This is wrong because they could overwrite sight modules if they have the same name. This was fixed to use a separate folder according to the name of the repository.
How to test it?
- For Sight installers, the CI deploy tests should be sufficient
- For the child repositories, a CI deploy test was added. You may also test manually.