On Lun 25 avril 2005 0:04, Mathias Bauer a �crit : > M. Fioretti wrote: > >> 2) the system package manager (rpm, apt, whatever) is not informed >> of what is added, hence it might not object later if you install >> with it some 3rd party thing that messes up what you added by >> hand to OO.o, Firefox, etc... > > Wether the system package manager needs to be informed depends on the > way the Add-On interacts with the system. If all Add-Ons are self > contained and do not need any other "packages" except the OOo > installation I don't see a problem.
Except they will need a particular python/c++... runtime, and what happens when you share your $HOME between different systems, when you update from a x86 to an amd64 or PPC64 box, etc Dump non-Standard UI on Mac people and you'll get lynched by Fitz followers. Dump non-standard packages on Linux people and expect the same. Mac people expect UI to just work. Linux people expect software management to just work. Windows people have long traded any semblance of sanity for a bit (if messy) software pool. Damn, if it was not so painful I'd dig out the first presentation messages of the Maven authors. They too couldn't believe someone may not want to accept self-updating. They too decided to force the issue. And now countless man-hours are lost trying to make Maven behave on Linux, because it chose not to follow the common installation paradigm (and it still does not work satisfactorily be it for distribution maintainers, Maven authors or Maven users) -- Nicolas Mailhot --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
