Tiny Core Linux
Tiny Core Base => TCB Talk => Topic started by: jls on September 09, 2009, 07:39:36 PM
-
let's say I marked for deletion an extension which depends on another, then I mark for deletion this other, appsaudit refuses, but this is wrong cause the first extension I marked 4 deletion was the only one depending on the second extension.
-
Each application should have their own spearation .dep list. If there is nested dependencies then it will take several iterations. What you see as undeleted may still 'depend' upon can be seen by the supplied reports.
Still there is much clean up that needs to be addressed with the .dep lists.I often see such reporting in the forums and therefore appsaudit is only as good as the dep lists.
Having an open community development providing such lists needs to be taken into consideration. Perhaps after moving to a single extension type, will make many things easier to manage.
All this need to be taken into consideration. Appsaudit is no panacea, nor will it ever likely be. However the reporting is useful and as the .dep lists become more reliable and not nested, things will only improve.
-
jls, I see what you are saying and will make more improvements to cover such case.
Via the reporting features, one should be able to unravel and mark for deletion others in that dependency chain. It will only be by use and over time that it will improve, as is the case with all software.