apps audit tool - Is it suppose to work this way?

[bigpcman]

I noticed that the apps audit tool "list dependencies" and mark for deletion list are different.

For instance if I install opera10 as the only extension in the "optional" directory I get the following tcz files:

xorg-7.5.lib
expat2
fontconfig
glib2
openssl
qt4.x-base
opera10

When I list dependencies for opera10 in the apps audit tool I get all the above minus opera10.


But when I "mark for deletion opera10 all that shows up is:
opera10
qt-4.x-base
fontconfig

... and when I reboot the above three extensions are removed but all the others remain in "optional".

This doesn't seem right. Am I missing something here? This makes removing applications a bit confusing.


tested on tc3alpha7

edit: Tried this on  shiretoko.tcz and the results are the same except of course there are even more files left behind in "optional" after the "mark for deletion" and reboot operation since  shiretoko.tcz has more dependencies.

[althalus]

it only removes opera's immediate dependancies - The extensions left behind are the deps of deps, so it would seem the remove tool is not recursive.

[roberts]

As mark for deletion existed before I implemented recursion.
The tce.db is recursive so adding such will be easy. See tce.db opera10 item.
In the mean time use the option Display All with No Dependencies

[althalus]

tce.db? Where can I find more information on this tce.db?

[roberts]

Since all of my code is limited to only that which is included in the base Tiny Core, tce.db is a created on the fly awk database. Well, actually even more limited, busybox awk database. See tce-audit for all the gory details. 

[althalus]

Hmm, haven't actually looked at the code for the audit tool.

Most likely I'll be able to work out the answer for myself after I've seen the code, but wouldn't it be possible to extend this tce.db to be something that the appbrowser updates when downloading a new extension, and the tce.db can then be added to .filetool.list, and thus greatly improve performance of the audit tool?

The current ability to completely rebuild the db obviously still included for when someone plays with their extensions directory by hand or doesn't include tce.db in their backups.

[roberts]

There is always many ways to accomplish the same thing. But with the frequency of updates to the extensions and in particular their dependencies, I felt is best to be sure to have the latest at hand when performing an audit. It is really the same philosophy as booting to pristine state to ensure that the most current dependencies are processed.

Also one's personal collection of extensions should be far smaller than that of the official repository. It is also assumed that one has easy and fast Internet access.

tce.db is located in the tce dir along with the extensions and is therefore not in the backup.

[bigpcman]

As mark for deletion existed before I implemented recursion.
The tce.db is recursive so adding such will be easy. See tce.db opera10 item.
In the mean time use the option Display All with No Dependencies

Recursive removal of an extension and it's dependencies (all those not used by other extensions) will be a welcome addition to the tc tool set. I look forward to your implementation.

[althalus]

There is always many ways to accomplish the same thing. But with the frequency of updates to the extensions and in particular their dependencies, I felt is best to be sure to have the latest at hand when performing an audit. It is really the same philosophy as booting to pristine state to ensure that the most current dependencies are processed.

Yes, of course, Sleep deprived brains don't always follow thoughts through to the logical conclusion. Speaking from experience, it can take upwards of 5 minutes to build the database on a moderately powerful machine, (though that may be because I tend to experiment with a large variety of different tools) hence the original thought.

[roberts]

As mark for deletion existed before I implemented recursion.
The tce.db is recursive so adding such will be easy. See tce.db opera10 item.
In the mean time use the option Display All with No Dependencies

Recursive removal of an extension and it's dependencies (all those not used by other extensions) will be a welcome addition to the tc tool set. I look forward to your implementation.

Completed for both 2.11 and 3.0. Will be in next posted cut.