Hi Marco,
Marco d'Itri wrote:
> > 1) Let the preinst maintainer script make a copy of the old screen
> > binary, provide a script to clean up this mess afterwards,
> > inform the user via debconf about the issue and his
> > possibilities (where the copy of the old screen is, etc.).
> >
> > Disadvantage: It's a non-dpkg-managed mess.
> I strongly recommend this solution, along with a proper debconf notice.
[...]
> /tmp is a good choice because the next reboot will automatically clean
> up everything (and obviously the old binary will not be needed after
> a reboot).
Thanks for that hint. This sounds better (and especially less messy)
than I thought! :-)
> > 2) Make screen 4.0.3 and screen 4.1.0 installable at the same time,
> > i.e. give them different source and binary package names.
> This would require a great amount of work
I fear so, yes.
> to fix a tiny problem which presents itself just for the length of
> the upgrade process, if at all.
Correct. It's an option nevertheless, so I mentioned it.
Thanks for your insight!
Regards, Axel
--
,''`. | Axel Beckert <a...@debian.org>, http://people.debian.org/~abe/
: :' : | Debian Developer, ftp.ch.debian.org Admin
`. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE
`- | 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
