Off-Topic > SCM EXtensions
SCM Basics
V.Krishn:
Current scm method is ok. It is also intended to run apps in its own Sandbox environment,
But I think it can still be done through tcz. Sandbox apps in tcz would be in /opt or /apps dir and compiled as per.
Symlink Method (Install) & Symlink Method (Un-Install) does take care of loading and unloading. Let me know if some step is left.
My steps does not concern on number of Dependencies. All dependencies can be clubbed in one scm or mix-matched.
During installation the scripts just tries not to do anything with existing symlinks pointing to /tmp/tcloop.
Example:
/usr/lib/<somefile> ---> /tmp/tcloop/<somepackage>/usr/lib/<somefile>
here while making a link "/usr/lib/<somefile>" the scm install script checks if it already exists and is pointing somewhere in /tmp/tcloop. If yes its a base system installation.
Rich:
Hi Jason W
So if I understand correctly, an scm is basically the same as how Xampp gets installed, except it
gets mounted as a squashed file system. All links to specific library versions and executables are
relative to the installation location to keep them out of the default path.
Jason W:
Rich,
Yeah, that is exactly the concept, at least in it's purest form. I did make an Xampp.scm early on, it requires some writable space inside it and to be installed into /opt. It required a little trickery, but it did work. I don't have it posted though.
uggla:
I would prefer if tczs were built exactly like scms but with (many) dependencies.
curaga:
uggla, do you mean just with a prefix of /apps? What would be the gain?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version