"Andrej N. Gritsenko" <and...@rep.kiev.ua> writes: > I've solved that in the > preinst script by 'rm -rf /usr/include/libfm' and I thought yet that was > a right step since upgrade 1.0.1 -> 1.0.2 went smooth.
Somehow that sounds like a really bad idea to me. Admittedly manually placing some file in /usr/include/libfm is pretty ugly, but I would still certainly not expect that upgrading the libfm package would remove it. Is that really good practice? Can packages "own" a directory, so that anything that the local admin puts there may be removed automatically? Best, -Nikolaus -- »Time flies like an arrow, fruit flies like a Banana.« PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87fw605th5.fsf...@vostro.rath.org
