symlink between tce directories

[softwaregurl]

If your like me, your going to have bunches of non-default tce directories.  To save hard drive space symbolic links between them work for me (knock on wood).  For instance if you have your default tce on hdd4 and one called mystuff also on hdd4 and what Opera in both this works.

Code: [Select]

sudo ln -s /mnt/hdd4/tce/opera-9.61.tcz /mnt/hdd4/mystuff/
On reboot it will load.  Remember any dependencies.  I doubt this will work between different partitions because they will not both be mounted at the time.

[mikshaw]

I once had a setup very much like that in DSL, and it worked well.  This was at a time, though, when the number of loop devices was severely limited. After the number was increased beyond anything I'd use, I just started automatically mounting all the apps I might need for that day.  The same seems to be true for tcz.

I could see this procedure being very useful for tce type extensions, since you don't want anything in RAM that you're not going to use.

[roberts]

I still support the "optional" directory, located just under the specified "tce" directory. Its purpose is for storing and upon demand loading/mounting of the less often used extensions.

In fact the "Download Only" of the appbrowser, stores the selected extension in the "optional directory". Using the File Menu of the appbrowser allows upon demand loading from the optional directory.

[softwaregurl]

I also put the backup file in the same directory so I have multiple unique configurations.

[mikshaw]

In fact the "Download Only" of the appbrowser, stores the selected extension in the "optional directory".

That was clever...wish I'd thought of that =o)

On the subject of the appbrowser, I was going to suggest the possibility of returning to the last-used directory when the user clicks the "local" button when loading multiple apps in the same session, but then I realized that adding that directory to favorites is just as easy.

[wiak]

I also put the backup file in the same directory so I have multiple unique configurations.

I like this method along with using symlinks in (various different) tce folders pointing to the optional folder and was about to suggest the same just prior to my noticing you had already posted the method. TC is astonishingly flexible.

Demand installing via the apps browser is also ery handy too, though it is nice to have various preset configurations (beats having to create lots of different re-masters, as users more commonly have to do in some other popular smallish downloadable distributions).