> > I don't meet the same problem with my 7.2 upgrade. It seems rpm scripts
> > were not properly run (/usr/bin/gcc & /usr/bin/emacs don't "belong" to
> > any package, so they were set up by script).
>
> This is interesting as I've just checked both of my 7.2 installations and
> these files are right where you guys suggest but I've also got the
> symbolic links in their appropriate places. Guess it's magic but I
> need some luck going my way :-)
Something wrong when a person starts responding to their own msgs but I
just thought of something. Did you guys do an actual 7.2 upgrade? I
always do a fresh install. I'm wondering whether this the problems you've
identified aren't a result of application location change and thus
something that's going to plague the upgrade path a lot as things are
moved to their "proper" places in upcoming releases.
What I mean by that is that if emacs was in /usr/bin with 7.0 and it was
moved in 7.2 (likely scenario), it's likely that a new version of it would
be put in place (that rpm opened and installed) before the upgrade script
would delete the old version. The result would be that the symbolic link
creation would fail (there'd be an emacs executable where the installer
was trying to make a link) and thus you'd end up without the links in the
proper place.
Cheers --- Larry
Keep in touch with http://mandrakeforum.com:
Subscribe the "[EMAIL PROTECTED]" mailing list.
