On Fri, Aug 25, 2006 at 09:05:26AM +0200, Sven Joachim wrote: > You are trying to fix #383971, but this is _not_ the way to do it!
I agree that the current approach is quite awful. > If the user had set the `yacc' alternative to manual, the preinst > script breaks that. A better way to do this would be to test first > if the system is actually affected by #383971, which should only be > the case if /usr/bin/yacc is not a symlink: > > [ -L /usr/bin/yacc ] || update-alternatives --auto yacc Looks good. But what if /usr/bin/yacc is an admin-installed script? I propose the following variety: [ -e /usr/bin/yacc ] || update-alternatives --auto yacc If we are upgrading from 2.3.dfsg-2, by the time the preinst script runs, the /usr/bin/yacc script installed by -2 should have already been removed, so the update-alternatives command would still run. If the admin wishes to manage /usr/bin/yacc manually, he presumably would put something there, and update-alternatives would not run. Does that sound okay? -- Chuan-kai Lin http://web.cecs.pdx.edu/~cklin/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
