Il 20/07/24 12:51, Willy Sudiarto Raharjo ha scritto:
this is a good point but it is not better to instruct slackpkg or
upgradepkg or whatever to not run douninst.sh when upgrading packages?
This seems a pkgtool feature lacks.
Generally, from my point of view, when a package is deleted the
package manager should not delete application data and this is a
common behaviour also in apt and dnf. There is a difference between
system configuration (replicable), application files and real data
(not replicable). A clean removal is meant by me like "the application
is no more present on the system" and should not consider user data
but only app configuration and binary/libs/etc of the specified
application.
Following your "clear all suggestion" and running an upgrade, being
the package removed and reinstalled, all useful data (reproducible
like configuration and not reproducile data like db records) will be
deleted making the new installation broken because user loses all
data, so is better to instruct pkgtool to assume the right behaviour
when upgrading.
Sometimes package manager should be updated with new feature or
existent features enhancement.
I'm pretty sure such behaviour (not deleting application data) is
already applied in slackpkg. It removes the binaries, documentations,
manual pages, and other files/directories created during installation,
but left out any other content created after the application is being used.
If you have a suggestion for slackpkg, you can send PR into this
repository: https://github.com/rworkman/slackpkg
Hi Willy,
thank you for the resource.
_______________________________________________
SlackBuilds-users mailing list
[email protected]
https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
FAQ - https://slackbuilds.org/faq/
