You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, most packages don't have autorm script populated in AOSC. This don't match the behavior of common dpkg distributions like Debian, where build scripts will generate post-removal scripts for maintainance.
One example is that in common dpkg distributions, dh_installdebconf will automatically insert debconf db_purge commands for packages having config to purge the debconf database when a package is purged. In AOSC we don't have this behavior, causing incomplete configuration cleaning when, for example, oma purge.
This is an example from an existing Debian installation:
Same as above, many other debhelper scripts insert corresponding purging behaviors in package building process. AOSC doesn't use debhelper and build process is done in autobuild, so this should be handled properly.
The text was updated successfully, but these errors were encountered:
ZeroAurora
changed the title
Automatically Generate autorm Scripts for Packages with config to Purge debconf Database
Automatically Generate autorm Scripts to Properly Handle Purging Behaviors
Feb 26, 2025
Currently, most packages don't have
autorm
script populated in AOSC. This don't match the behavior of common dpkg distributions like Debian, where build scripts will generate post-removal scripts for maintainance.One example is that in common dpkg distributions,
dh_installdebconf
will automatically insert debconfdb_purge
commands for packages havingconfig
to purge the debconf database when a package is purged. In AOSC we don't have this behavior, causing incomplete configuration cleaning when, for example,oma purge
.This is an example from an existing Debian installation:
Same as above, many other debhelper scripts insert corresponding purging behaviors in package building process. AOSC doesn't use debhelper and build process is done in autobuild, so this should be handled properly.
The text was updated successfully, but these errors were encountered: