On 2 May 2006 at 22:05, Kel Modderman wrote: > >place, so that custom scripts will stind find it. However I think this > >is a quite seldom cornercase, and I highly doubt this would satisfy the > >submitter. > > Well, lets wait and see if this would indeed satisfy Felix' bug report, > from Felix himself.
I think *definitely* you should leave this file in place; it's crazy to assume noone will have their own scripts that call wpa_supplicant. As far the general issue, I don't think the situation is quite as serious as Felix suggests, because it is trivial for the user to discover what's happened and fix it by reading the documentation. On the other hand, having a package upgrade silently break one's network configuration without warning is *far* from ideal, in my opinion. A message calling attention to this during the upgrade, with a reference to the docs and/or the wiki, would be very helpful. Best, Michael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
