/usr/bin/X11 --> ../X11R6/bin
/usr/include/{X11,GL}/{X11,GL} --> ../X11R6/include/{X11,GL}(I think these are what was left; I am not close to the test system right now. In any case, they are from the xorg install that .904 upgraded from.)
This is not too serious, because they point to nowhere. I am sure they result from this chain of events:
1. pre-904 xfree/xorg installations set up alternate paths to their
files: /usr/X11/{whatever} --> ../X11R6/{whatever}
2. With .904, everything is merged into /usr/{whatever}
3. But this merge tries very hard not to wipe out anything already
installed in these /usr/{whatever} directories, in case, I suppose,
the user actually had real directories there instead of symlinks to
the X11R6 installation.A simple sort of check like:
[ -L /usr/bin/X11 ] && rm /usr/bin/X11
early in the install (but not too early, you can't do it until you are sure the installation will complete --- otherwise, you will fail to install but you will wipe out part of the previous installation) is the sort of thing needed, I suppose.
But it is too simple. If, for some reason /usr/bin/X11 (e.g.) turns out to be a symlink, but a link to something foreign, then you have to decide what is appropriate:
1. Just eliminating it is easiest, although that will break the
system set up in this non-standard way;
2. Preserving it in this case is most likely what the user expects.
I hope this isn't too garbled, Regards, -- Ferris McCormick (P44646, MI) <[EMAIL PROTECTED]> Developer, Gentoo Linux (Sparc)
signature.asc
Description: OpenPGP digital signature
