Hi, Florent Rougon wrote: > Reason: if there were TeX files in any previous version of the package > (up to the previous Debian release), then mktexlsr *has* to be run.
Why weren't they in their own package then? Then if the package goes away you already have the postrm run mktexlsr because it's there in the old package and gets run when you remove it. I'd have split out the tex files (let alone because the dependencies on TeX stuff) and if you app really needs them make the app depend on *them*, not ship them in the normal packages. This is like comparable to programs/libs, where the (public) libs built from a programs' source package should also not be in package foo but in libfooX. In many cases this looks like packaging error to me. Exceptions might prove the rule. But I don't have an overview on how packaging like the above done currently in Debian.. > If there is nothing TeX-related in your package, don't run > dh_installtex... But there *is*. In texpower. Not in texpower-manual nor in texpower-examples. -p is just a workaround. dh_installmenu does not add update-menus to everything because one package produced has a menu file and is therefore called. It just adds the needed stuff to the needed packages. In contrast to that, dh_installtex when ran without -p adds its snippet to *every* binary package, may it have tex stuff in it or not. Anyway, I just worked around it by using -p and will keep it mind. Do whatever you think, but you are behaving completely different than many "normal" dh_*'s. Gr��e/Regards, Ren� -- .''`. Ren� Engelhard -- Debian GNU/Linux Developer : :' : http://www.debian.org | http://people.debian.org/~rene/ `. `' [EMAIL PROTECTED] | GnuPG-Key ID: 248AEB73 `- Fingerprint: 41FA F208 28D4 7CA5 19BB 7AD9 F859 90B0 248A EB73
signature.asc
Description: Digital signature
