Re: [gentoo-user] portage inconsistency?

Neil Bothwick escribió:
> On Mon, 06 Aug 2007 10:45:25 +0200, Abraham Marín Pérez wrote:
>
>
>> Now think there's a new version available of LIB, let's say version
>> 2.1, but the latest version of APP is still 1.0. If portage performed a
>> deep update by default LIB would be rebuilt, but no APP, what would
>> cause broken dependencies on APP (remember LIB is a dynamic library).
>> However, is you don't update LIB unless you update also APP you will
>> prevent this problem*.
>>
>
> SLOTs deal with this problem, allowing you to have LIB-1.0 and LIB-2.0
> installed simultaneously.
>

I'm afraid you misunderstood what I said. As you said, slots let different versions of the same package being installed in your system, however, that's only done when you REALLY need to do so; one of the cases in which you would have such a necessity is the one of a library which changes its API through versions in a way that breaks backwards compatibility. In this case you may have apps using the old API and apps using the new one, and hence you would need both versions installed.

However, if you can go with only one version slots aren't used, can you imagine the great amount of garbage installed in your box if you had to use a new slot for every new version of a package? That's just crazy.

In conclusion, if you update a library and uninstall its previous version (which you'd do very often, even if you haven't noticed it before) you may need to rebuild the apps using that library as well, there's no way you escape from that.

Abraham

-- 
gentoo-user@gentoo.org mailing list