<br><br><div><span class="gmail_quote">2005/10/23, Peter Selinger <<a href="mailto:selinger@mathstat.dal.ca">selinger@mathstat.dal.ca</a>>:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
...<br>I am a great fan of backwards compatibility. Especially if you batch<br>update a lot of packages, it is a pain to have to track down<br>documentation for unexplained broken behaviors.<br><br>I think we should do the same when we rename the "newhidups" driver.
</blockquote><div><br>
so do I.<br>
<br>
The driver name change is a long standing point, and more and more
annoying me in my Debs. And we'll once again reach a high level of
driver names change with 2.2, that point is sure!<br>
<br>
I'm currently more inclined at making some helper script that will
replace the driver name in your conf (obviously making a backup of the
orig files). This one would be called by the user at source install
time, or by the package (preferably after having informed the user).<br>
</div>The symlink and the stub doesn't solve the problem, but only
annoy the user (if this one sees the message!). So let's go directly to
a solution...<br>
<br>
Any perl (or other well supported scripting) monger out there to take over that one? <br>
<br>
Arnaud<br></div>