Patrick Shanahan wrote:
* Hylton Conacher (ZR1HPC) <hylton@global.co.za> [01-22-05 14:17]:
When you say they do not require lib's, I'm assuming that they do not share any common dependency files that might be changed if the program was updated, therefore allowing the reverse upgrade(downgrade)?
Unless you use the rpms provided by one of the SuSE repositories, there should be *no* relation to what version you are running unless you run something like galeon which relies on the mozilla package and is sensitive to version. Good
Can I therefore assume, in a simplistic way, that if I was updating KDE from 3.1 to 3.3 they would both be affected because they rely on the X configuration being a certain way so thy can work.
Understand what *they* say about _assume_. :) Whilst I might be a pain in the ass, I do not want to call you one :)
I don't understand where you are comming from. KDE runs on X and is dependent on X. Mozilla and OOo run on X, not the window manager which is what KDE is. Mozilla and OOo also run on Xfce, gnome, ...
Perhaps you need to reconsider your question and ?? rephrase ?? You basically confirmed what I thought, that by updating either of the packages *should* not affect the other as there are no shared components that the upgrade would break ie if Mozilla 1.7.2 required a common system program/library to both it and OOo to be a newer version than what was installed, but the OOo 1.1.4 could quite satisfactorily work on the older version of the system file/library, then I would upgrade OOo but not Mozilla as the newer system file/library might 'break' OOo 1.1.4.
Is that better explained/understood?
Mozilla/OOo are not dependent on KDE KDE is not dependent on Mozilla/OOo (AIUI) Is there perhaps a common system file that Mozilla and OOo share?
-- ======================================================================== Hylton Conacher - Linux user # 229959 at http://counter.li.org Currently using SuSE 9.0 Professional with KDE 3.1 ========================================================================