Hi, > Is it prepared for the package "usrmerge"
Not at all, and I don't plan to dig into the "cruft" engine to make it happen. I liked the idea behind cruft, that each file of a filesystem should be accounted to some package; but definitively not the original engine. That's why I wrote cruft-ng, give it a try. This one is UsrMerge compatible. Is a "Breaks: cruft" in usrmerge package enough to please you ? It is lowest hanging fruit; there's certainly still much to do. Still hoping that one day much of "cruft" functionality would be merged into packages&dpkg. The cruft-common package shared accros cruft & cruft-ng with the definitions wil remain. Le mar. 8 oct. 2019 à 21:33, Harry Haller <odysseu...@mailbox.org> a écrit : > My call of cruft: > #cruft --ignore "/root /home /mnt /proc /sys /Dummy /Schafott /Pax /dev > /lost+found /opt /run /srv /tmp" -r ~/Cruft.report Sorry but not all of this has been re-implemented yet in cruft-ng; but the defaults are better (always ignore /sys /root /home /tmp) and most are inherited from "mlocate" database. > Since more than 10 years (felt) the debian-users waste their lifetime > with this - at best - "sid"-package. > Nothing justifies, that cruft finds it's way always into whatever is stable at > the moment. > > Please be consequent and kick it out of the stable releases until it works > (some day in a distant future)... One could remove the "cruft" binary package and I wouldn't be the one to complain; as long a "cruft-common" is still built. I need more feedback. Greetings RépondreTransférer
