Wolfgang Pfeiffer wrote:
>
> First: thanks for your time, Michael.
you are welcome to it. it is worthless anyhow. check the archives.
> > also be aware that goofy stuff like library dependencies and suchlike
> > may break your old software even if all your files remain intact.
>
> ... you mean that even if my current libraries are 'cleanly' connected to
> each other that there's always a small risk some stuff will break with the
> update, right ... ?
well, if your current, cleanly-linked object files (libraries or
whatever) depend upon shared libraries which go away during the upgrade,
you'll have trouble. an instance i've run into from time to time is
something like this: /usr/local/bin/foo depends on shared library
/lib/libbar.so.1; when the package containing libbar.so.1 is upgraded,
libbar.so.1 goes away and gets replaced with libbar.so.2. next time i
run /usr/local/bin/foo, i get missing shared library errors.
not terribly frequent, probably fixable in most cases, just mildly
annoying and it seemed worth mentioning since you asked. i sometimes
cheat by bringing back the .so files that rpm blew away, i'm sure i'll
go to unix hell for it but that's my problem. ;)
--
~~~Michael Jinks, IB // Technical Entity // Saecos Corporation~~~~
We write precisely
since such is our habit in
talking to machines; -- anonymous
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
