On Sun, 2022-10-23 at 01:08 +0200, Alexandre Detiste wrote: > This DebHelper works this way: > * the "debian/cruft" list merely register the glob patterns, > * and "debian/purge" list also an "rm -rf" stanza in postrm/purge. > > As a bonus there's now also a new "cpigs" command, working akin to > "dpigs" from Debian Goodies to list the biggest volatile data producers. Thank you for your work on this, being able to register files generated at install time by maintainer scripts or even at runtime by system maintainence tools to particular packages is a very useful feature for keeping all the files on a system more easily managed. Potentially it could also prompt users before removing packages that have registered data that won't be removed on purge, for example if a package creates at the sysadmin's request a dir in /srv to host a website, removing the package could warn about the directory. Or removing postgres with databases present could warn about those. I do worry about users removing files that they don't understand, based on feedback by cpigs/cruft-ng, but they do that already so... :) > The plan now is to have a new option that dumps the whole > matching result database as .json with individual file size > for jq consumption or in my case Jupyter; > this instead of implementing older requests (#291823 #487458 #527285). An ncdu or mc style interface (or plugins for those) to view cruft on a system sounds very useful in addition to the data export. -- bye, pabs https://wiki.debian.org/PaulWise
Attachment:
signature.asc
Description: This is a digitally signed message part