> I see that the code is both in the (unused) preinst and in > lilypond-data.postrm. It's actually not clear to me whether preinst or > postrm is the best place to do this. The argument "pro" preinst is that > one could check the old version, and only trigger the removal if we are > upgrading and the old version is older than the last change to the > fonts. The arguments "pro" postrm are that you don't need a > Pre-Depends, and that file removal makes more sense in a removal script > and should also be done upon package removal, not only upgrade (as your > postrm script does, correctly). The preinst stuff is there to deal with older buggy versions of the package that did not have a postrm to remove things. But this does not mean it is something we should still care about, or that this is anything like the right way to deal with it.
Attachment:
signature.asc
Description: This is a digitally signed message part