Hi again, I digged deeper ( https://codesearch.debian.net/search?q=pkgos_dbc_postrm&literal=1 ) and I know realise that pkgos_dbc_postrm work at the same level as, for example "deb-systemd-helper" that got injected in so many postinst scripts; and not at the same level as dh-cruft that changes how maintainers scripts get templated.
So my original idea won't work. Would you be ok for 15 merge requests on Salsa that translates a bit of postrm.in into a debian/purge file + adding dh-sequence-cruft build dependency ? This won't hurt back portability, helper was basically done in 2022 already. codesearch 'pkgos_dbc_postrm path:postrm.in' --only-package | wc -l 15 Greetings Alexandre Le jeu. 21 mai 2026 à 14:03, Thomas Goirand <[email protected]> a écrit : > > Hi Alexandre, > I'm always happy to receive good advice, especially from someone like > you who has helped me to make a lot of improvement on the OpenStack > packages thanks to so many bug reports. > > I had a look into snake4 as you suggested, and the only thing I could > see is dh-sequence-cruft as build-depends, and snake4.purge containing > /var/games/snake4.score. If I understand well, what it's doing is writing: > > /usr/share/cruft/rules/<package> > > which contains a list of folders owned by "my" package once it's removed > but not purged. Am I correct? > > So if I understand correctly, I'd only have to add something like: > > echo "/var/lib/<package>/** > /var/lib/<package>" >/usr/share/cruft/rules/<package> > > in my postrm scripts? > > Please let me know if I understood correctly. > > Cheers, > > Thomas Goirand (zigo) >
