On Fri, 29 Dec 2006, Martin Costabel wrote:
> I think I can smell the bug in update-alternatives that is responsible for
> this. Claus, just to confirm my suspicion, could you please try the following:
> 1. Remove the symlink /sw/bin/sed if you created it in the meantime.
> 2. Run
> update-alternatives --display sed | head -n1
> to confirm that "status is manual".
> If it says "status is auto", run
> sudo update-alternatives --config sed
> and choose 1 or 2.
Yes, status is manual. (BTW, I only have gsed installed.)
> 3. Run "fink reinstall sed" and check if the symlink exists.
> I suspect it doesn't.
Correct, it doesn't exist.
> 4. Run
> sudo update-alternatives --auto sed
Symlink /sw/bin/sed exists after calling this command.
> 5. Run "fink reinstall sed" and check if the symlink exists.
> I suspect it does exist now.
Yes, symlink still exist.
> It will actually have been created in step 4, but even if you
> remove it once more, it will come back in step 5, and it will
> stay with you henceforth.
I did a "fink remove sed" and the symlink was gone as well. After doing
a "fink install sed", the symlink has been created, as you expected.
Thanks for this hint!
> If you confirm this, I'll take the discussion to fink-devel in order
> to find a solution.
I guess that "update-alternatives --auto sed" should have been called
the first time I installed any sed via fink. Am I right?