Installing new tce version over existing one.

[bigpcman]

I'm wondering what the consequences of installing a new tce over an existing one are? If the new tce installs new or different dependent support files and libraries does the cleanup have to be done manually. Is a manual check required before an update?

[curaga]

The cleanup is done by a reboot, and after that only the new files are available (HD installs aren't officially supported persistency in /usr/local is a middle case, if an extension is put there it would need manual cleanup)

Usually an update works just fine.

[bigpcman]

I tried reinstalling using the app browser emelfm2 and found that that the app browser does not appear to overwrite the existing emelfm2 in the tce directory. The app browser just instantly responds with the message installed. I had to manually delete the emelfm2 from the tce directory to get the new install to work.

[tobiaus]

I had to manually delete the emelfm2 from the tce directory to get the new install to work.

while that may be a slight inconvenience, it's easy to believe it was designed exactly that way, and the fact is that if a tce won't overwrite an existing file, the "package management" (i'll call it that) for tc is less powerful... and relatively secure. when you think of it like that, it's probably worth keeping it the same.

[Kingdomcome]

I believe appbrowser looks in /usr/local/tce.installed/ for a list of installed apps.  Deleting the file with the name of the extension you want to re-install, or simply download again allows appbrowser to perform the action you choose.
If you use the ppi method with a tclocal, there may be other complications that would need to be considered.