and thanx for the interest...
I updated my patch and sent it to pankso but my intentions weren't accepted yet. Maybe I was not clear enough about the description / usage.
You'll find the latest version of the patch attached, if you'd like to use it.
[Edit: I fail in uploading the patch even as .txt file :-( sorry for the moment]
What the extension does is (as you might comprehend looking at the script):
block 102- ):
extend the usage information
block 635- ):
upon installation of a package, add the name to /var/lib/chosenpkg.lst
block 765- ):
- collect dependency-information of all installed packages (out of "/var/lib/tazpkg/installed/[pkg]/receipt)
- check if the individual package is system-relevant (see below) or listed in chosenpkg.lst
- check if the individual package is listed in the dependency-collection from above
If the package is neither system-relevant nor deliberately chosen (> chosenpkg.lst) AND no package depends on it, then it is orphaned and is offered for removal. If you choose to remove it, the loop is broken and the check starts from the beginning, since other packages (with "lower" name) might be orphaned now, too.
If you deny removal, then you have deliberately chosen the package now and it is added to chosenpkg.lst.
What is suboptimal up to now:
- As a starting point, you have to perform an initial unorphan run to create chosenpkg.lst; ideally, if the routine was used from the beginning of SliTaz setup, this would have already been created, since every deliberatley installed package would have been logged already.
- I don't have a clear picture of which packages really are system essential. Especially the "level of ambition" (using XOrg or not, choice of Window Manager / Desktop environment) does have an influence on this. On the other hand, this might not be grave as long as you know what you are doing (but who really does ?!?)
- Unorphan patch works (at least on my machines) like a charm using the command line but up to now fails in the "graphical way" using tazpanel due to lack of interactivity during the (de-)installation-process.
I'd highly appreciate a revival of this topic, because up to now I seem to be the only one using my patch...