On Friday, February 21, 2003, at 04:40 PM, David R. Morrison wrote:
The problem is that the removal of files is happening in PostRemove, outside
of dpkg's control. But if you can think of an alternate way to solve this
problem, I would love to hear it.
Have one of your scripts edit the var/lib/dpkg/info/tetex-base.postrm. I don't have a copy of Debian policy in front of me to check where you could do this (probably even in tetex-base pre-inst, but I'd have to check that), but I'm sure there are several places.
I think you can force dpkg to try the postrm from the new package by just replacing the old postrm with something that will fail, like "exit 1"
Yes, this method is evil. But I'd argue less evil than telling people to reinstall a package.
PS: Please don't demolish configuration files without asking the user --- check tetex-base.preinst.
------------------------------------------------------- This SF.net email is sponsored by: SlickEdit Inc. Develop an edge. The most comprehensive and flexible code editor you can use. Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial. www.slickedit.com/sourceforge _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
