Re: gambas residual gumph

[Benoît Minisini <benoit.minisini@xxxxxxxxxxxxxxxx>]

Le 07/11/2024 à 19:06, Bruce Steers a écrit :
> What's your view Ben?
>
> is this a problem of the toolkits that should be handled upstream or 
> should the interpreter be removing these folders?
>
> Should we "expect" residual garbage to be left on our disks if using 
> Quit and/or testing/debugging and handle it ourselves as I have done?
>
> gambas does seem a little , er , messy , in not cleaning up after itself.
>
> Do you have a surprisingly large amount of dead gambas folders on your 
> system too?  (try my script out)
> Respects
> BruceS

Everything in the '/tmp/gambas.<userid>/<pid>' directory is 
automatically removed at process end, unless the process crashes.

The directories named '~/.cache/org.gambas.*' are apparently the cache 
for WebKit, and is never destroyed.

The different 'org.gambas.*' names come from the application name 
created at startup to workaround the problem with Wayland that is still 
not able to allows an application to define its window icon without 
having to create an application name with its desktop file.

I could remove the WebKit cache folder automatically (or optionnally for 
those who want to write a web browser). I will check that.

'~/.local/share/gambas3/wiki~' is just a backup of the previous wiki. It 
is created each time you download a new one, and maybe it is useless.

'/run/user/<userid>/gambas3' is used for storing the shared cache of the 
JIT compiled code, so it should be kept. If you remove it, it will force 
the recompilation the next time a Gambas program needs it.

As for '~/.local/share/org.gambas.*', I don't know what creates them. :-/

Regards,

--
Benoît Minisini.