extension loading suggestions

[robc]

I have a few suggestions for how TC operates with extensions:

1. Have an option in Appbrowser to search the extensions' .list files. This lets you search for a specific file using the appbrowser rather then having to load a web browser extension to search the web to see which package should contain a particular file and prevents searching through the file lists manually to verify if the file exists in that extension (can be quite difficult with large extensions).

2. A hybrid mount/install mode using size limits. Include a flag (i would imagine in /etc/sysconfig) to specify a size limit for a tcz to be installed into RAM. For example the size limit is set to 100k, all extension that have a size under 100k would be installed into RAM where all extension over 100k are mounted. This can be used to 'automate' the install/mount decision rather then specifically stating if the extension should be mounted or installed. It can also be used in place of tcz2ram.flg and in cooperation with tcz2ram.list. Also a boot time switch can be added so the user can specify the size limit, ie tczlimit=100k, tczlimit=none.

3. Show the actual size the extension requires. This would include the extension's size plus the size of all of its dependancies. Gives a more accurate look at what resources are needed.

4. Remove the .tcz extension from the files listed in the dep files. ie 'libcups' instead of 'libcups.tcz'. Reduces the size of each dep file and prevents typos from extension makers.

Any other suggestions or comments or concerns are welcome.

Rob

[althalus]

I have a few suggestions for how TC operates with extensions:

1. Have an option in Appbrowser to search the extensions' .list files. This lets you search for a specific file using the appbrowser rather then having to load a web browser extension to search the web to see which package should contain a particular file and prevents searching through the file lists manually to verify if the file exists in that extension (can be quite difficult with large extensions).

I like that idea.

3. Show the actual size the extension requires. This would include the extension's size plus the size of all of its dependancies. Gives a more accurate look at what resources are needed.

That would be misleading. Extension A needs 20MB, extension B also needs 20MB. OK, together they need 40 MB. But what if they share 80% of their extensions, and installing them both only requires 25MB?

A better approach would be something like apt's way of doing it: "After installing, you will use up an extra xxxx[KM]B of storage space" taking into account extensions already installed.

4. Remove the .tcz extension from the files listed in the dep files. ie 'libcups' instead of 'libcups.tcz'. Reduces the size of each dep file and prevents typos from extension makers.

Rather, make the extension optional.

[robc]

Quote
3. Show the actual size the extension requires. This would include the extension's size plus the size of all of its dependancies. Gives a more accurate look at what resources are needed.
That would be misleading. Extension A needs 20MB, extension B also needs 20MB. OK, together they need 40 MB. But what if they share 80% of their extensions, and installing them both only requires 25MB?

Perhaps this doesn't need to be included in the base. Since TC is all about options, why not create a full package management system and make it available as an extension? The current appbrowser (or even a stripped down version) can be left in the base so TC can still handle extensions, but if the user wants more they can add the package management extension which has a lot more capabilities.
The correct size requirements that are needed to install a specific extension would have to be calculated based upon what is already installed.