On 02/02/2005 11:35:57 PM, seth vidal wrote: > > The problem I've seen is that even the repositories aren't sure who > they > are and are not compatible with. So trusting a repositories claim > about > what it is compat or dependent on is a dicey affair. This is true - and breakages happen. For example - I maintain a small repository that had some stuff linked against liboil 0.2, which I also provide. I depend upon Fedora Extras and rpm.livna.org A week ago or so Extras added liboil 0.3 - which then broke ability to update because the shared library versioned. Some of the apps can be easily patched to build against liboil 0.3 but some (so far) I haven't had luck with. I changed the name of my package to compat-liboil and that allows yum to work again, and soon I will have all the packages that use liboil using the Extras build, but extras doesn't know (and shouldn't know) about me, so this kind of thing can happen. That's why I think it is important, especially for larger repositories, not to update shared library API's - it breaks small specialty repo's. In this case, extras did nothing wrong because they did not provide liboil 0.2.
