Tiny Core Extensions > TCE 1.x

tce-uninstall

<< < (3/5) > >>

jls:
why this tce doesn't work with tcz?

Jason W:
Though there is a tcz-uninstall avalable, there are going to be some changes that affects this uninstaller and will make it available across all supported modes.  Given that, I may combine the two uninstallers to work with both tce and tcz since many run a combination of the two.  That way dependencies are accounted for whether they are installed as tce or tcz.  I will shoot for that in mind and hopefully come up with a solution in the coming week or so.

Though I will leave tcz-uninstall as an extension since some folks will not want to uninstall tce's.

Jason W:
I did update tce-uninstall to work across all running modes by fetching the file lists from the server, but I will leave tce-uninstall and tcz-uninstall as two seperate utilities since the two extension types are two very different animals.  This uninstaller was made to mirror the install process and use the same dep files.  The dep files work only with the same extension type as they belong to, and the uninstaller should too.  Keeping the uninstall utilities seperate keeps things more congruent with the base system.  Not that having a universal uninstaller is a bad idea, I did ponder it for a while. 

jpeters:
I still don't quite understand how uninstall works.  For example, if I load OO.tcz  from my optional foldler,  it has expat, fontconfig,and libxm as dependencies. After loading/uninstalling, nothing is added or removed from /tcZ, and the deps remain to be loaded upon reboot.  I don't know if things would be different if OO was installed directly from the appsbrowser into tcZ. If the deps aren't being used by something else, they would be deleted?  Only if they were installed with OO?  Sorry to be dense about this.     

Jason W:
You're not being dense.  There are these checks that have to be satisfied by the package being uninstalled and it's dependent ones if they are being removed too: check for files in use, check to make sure all files are beneath /usr/local.

If you are running a mixed system, tcz along with tce, then only tce installed extensions are dealt with.  Tcz-uninstall is to be used to remove them.  The tcz uninstaller has a check to see if files are in use, but dependencies are not dealt with.  I can add dependency removal and will when I have some time making it the same as tce-uninstall.

It makes no difference how the extensions are installed, the dependencies are gathered by the .dep files that are downloaded when the uninstaller is first run.  Say you install OOo, expat, fontcofig, and libxml as tce's.  Bringing up the uninstaller and removing OOo will not bother those other three since they are dependencies of OOo. Nothing depdends on OOo so as long as it's files are not in use and it is all beneath /usr/local it will simply be uninstalled.  If some of the dependent apps of a tce being removed are tcz's, they will not be dealt with but they can be removed by tcz-uninstall.

The uninstaller does not remove extensions themselves that reside in your */tce directory.  If you are running totally in RAM, they are removed from /tmp/tce upon loading.  I could add an extra dialog question that would ask if you want to remove the extension(s) in the tce directory as well as uninstall them from the system.  That would make it easier to maintain your /tce folder selection instead of picking through it manually.  But I don't want to mess with the contents of the optional directory since those apps are loaded manually at will.

Navigation

[0] Message Index

[#] Next page

[*] Previous page