Bug#183357: Making a symlink in the post installation script?
Tore Anderson
Tore Anderson <tore@debian.org>, 183357@bugs.debian.org
Fri, 18 Feb 2005 20:17:12 +0100
As I realized the current Exim version in Sarge is probably not going
to be the released one, I started thinking a bit about this issue
again, hoping that there are still time to resolve it.
And then it struck me. A solution so simple that I feel really
stupid having spent a lot of time masterminding all kinds of complex
solutions earlier in the bug log. (Well, "masterminding" might be
inappropriate as nobody but me thought the ideas were any good. :-)
Anyway: Why don't we just simply check in the post installation
script of exim4-base if any of the problematic files from Woody's exim
package is present, and if they are not, make a symlink from "exim" to
"exim4" in /usr/sbin. This way all new installations will get the
regular binary, and so will all upgrades that doesn't have the
problematic files from Woody's Exim. The postinst could also be made
to print a little warning if the problematic files were detected.
The postrm would of course need to take care to delete this symlink,
too.
I cannot see any problems whatsoever with this solution, not
policy-wise, not implementation-wise, nor functionality-wise. However
it's so simple that surely someone must have thought of it before and
rejected it? So I wonder if I'm making a fool out of myself right now
by not realizing somthing blindingly obvious, but hey - if I don't and
it makes it into Sarge it was certainly worth taking the risk. :-)
So - what do you think?
Kind regards,
--
Tore Anderson