https://bugs.kde.org/show_bug.cgi?id=392461

Dan Jensen <ad...@leinir.dk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ad...@leinir.dk

--- Comment #5 from Dan Jensen <ad...@leinir.dk> ---
(In reply to Aleix Pol from comment #2)
> Plasma/KPackage should tell KNewStuff to uninstall a Plasmoid when a
> plasmoid is uninstalled.

It seems to me like the "proper" way to do this would be to make it possible
for the KPackage installer to hold some kind of way to call a command
post-uninstall (the way e.g. rpm and deb does)... That would then make it
possible for KNewStuff to inject such a step, so e.g. kpackagetool would be
able to request KNewStuff to remove all references to the content item having
been installed.

Another option would be to add functionality to KNewStuff, which might have
another step to ask for up to date information from the tool used to install
something. This would require e.g. kpackagetool to remember where something was
originally installed from, so we could do e.g. CheckStatusCommand=kpackagetool5
--install-status %f (the way the InstallationCommand and UninstallCommand
entries work right now). This could then be run during the cache load step, and
while this would arguably be considerably heavier than the current state, the
current state is also not exactly brilliant, so...

i did think that it might be possible to do something like having kpackagetool
know when something's initially been installed through knewstuff, so that it
would be able to ask knewstuff to do the removal. But, that seems like that
would be an unnecessarily roundabout way of doing it, especially considering
kpackage would then have to be called again, from knewstuff, to perform the
data removal (because knewstuff loses track of that data when kpackage installs
it, which in turn would be why this problem exists in the first place...).

Thoughts?

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to