Bug#3276: screen upgrade trashes running sessions...
-----BEGIN PGP SIGNED MESSAGE-----
joost witteveen, in an immanent manifestation of deity, wrote:
>Answer: dpkg -i screen also runs the postrm from the old screen.
>and guess what: it's got a "rm -rf /tmp/screens" too. This is
>no surprise, it has to have (otherwise you can never remove
>screen completely).
>
>So now what? Make /tmp/screens a "configuration file"? This seems
>hardly what "configuration files" were divised for.
>
>Although I agree with you that the current behaviour is less than
>perfect, I challenge you to come up with a better way.
>(the testing then has to be done in postrm, but postrm *should*
>get rid of /tmp/screens).
Check out the following in node:
(guidelines)Maintainer script arguments and how dpkg does things
Essentially, you'll only want to rm -rf /tmp/screens when your postinst
gets purge as an argument on the command line.
When upgrading to a new version of screen your old postinst will get an
argument of "upgrade vers-no." on its command line. If you take a look
there, your scripts and screen users will be happy...
Darren
- --
<torin@daft.com> <http://www.daft.com/~torin/> <tnd@iswp.org> <torin@io.com>
Darren Stalder/2608 Second Ave, @282/Seattle, WA 98121-1212/USA/+1-800-921-4996
@ Do you have your clothes on? I probably don't. Take yours off. Feel better. @
@ Sysadmin, webweaver, postmaster for hire. C/Perl/CGI programmer and tutor. @
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQCVAwUBMcHwMo4wrq++1Ls5AQGsfwP7BuLrDnRlh9VEEKgqEcT3Ij5Up3awOWVz
+4wtgxiKvWgTwer0t1T2/luueyvDMzm40kYzDvs55ZprSX+BRQ3zu7wUvoW7tGtM
SB8UjA17j/i8E6T6AT7bNBKxnJHTEjYKdO5f+hLxGtvgy4uSfu+U109LcrqNJsDe
sf/YqvO5oIM=
=cw80
-----END PGP SIGNATURE-----
Reply to: