Hello Marco,
just for the records:
I think your procedure is wrong, because /etc/modules could have
existed before m-i-t was installed. You check this during postinst, and
leave the file as it is, which is recommended in chapter E2 of the
debian policy. So far so good. But later during postrm the package
nevertheless deletes the file, even if the file existed before. For
this case I cant find a really relevant policy statement. Is there no
general behavior prescribed? I prefer not to delete the file.
a last question:
If the file neither belongs to the package, nor is a conffile of that
package, how can I be sure, to which package the file belongs?
With your argumentation any package (for example yaird, ... ) could
remove the file, just because the package thinks the file belongs to
it!?
Regards,
Kiro
signature.asc
Description: This is a digitally signed message part.
