Paulo Cavalcanti wrote:
FreshRPMS sometimes replaces system libraries with newer versions.
This is done to provide new features but it can cause conflicts. One
recent example was that libgpod was updated there. Core was providing
libgpod-0.3.0 and freshrpms updated that to libgpod-0.4.0 not noticing
that they were not ABI/API compatible. That's causing an
incompatibility with Core and Extras.
Core applications for me are the ones needed to run a server.
libgpod is not the case. If this breaks, no one is going to jump off the
bridge.
Every repo will have problems along the time. Livna had a lot recently.
This is unavoidable. The point is: are the these problems corrected fast?
How do you define 'corrected' when different repositories in your yum
configuration provide different versions of the same library RPM and
other applications in each repository has dependencies on it's own version?
What I really like in linux is that there is a real person behind
everything.
ATrpms - Axel Thimm
Dries - Dries Verachter
Dag - Dag Wieërs
Freshrpms - Matthias Saoul
KDERedHat - Rex Dieter
Livna - ????
I have a profound admiration for the work of all the people I listed above.
Sometimes, I would have done things differently, but I would never FUD
any repo because of that.
Conflicts aren't caused by FUD, they are caused by different versions of
the same-named package existing in different repositories mentioned in
your yum configuration. The repositories that do that have their
reasons for doing it, but if you include them along with anything else
that doesn't stay coordinated you are likely to have conflicts.
--
Les Mikesell
lesmikesell@xxxxxxxxx
