Enrico Weigelt wrote:
> * Luca Barbato <[EMAIL PROTECTED]> schrieb:
>> Enrico Weigelt wrote:
>>
>>> It mixes up diffent things to one and just introduces new 
>>> problems instead of solving anything. I could live with that, 
>>> if it's for supporting different ABIs, but it obviously isn't.
>>>
>> No?
> 
> In this case not - it's used to mix up two different packages.
> 
> 
>>> gtk1 and gtk2 are completely different packages, they're not
>>> compatible. So why should they be one package ? Just because
>>> they share some ideas and the name ?!
>> Because gtk-2.xx is originated from gtk+-1.2.xx and you still 
>> have a common set of widget API ?
> 
> The APIs are incompatible. 
> 

They are still the both evolutions of the same development tree, they
are the same package, just different versions. If we changed the name of
a package every time there was an API break, we would literally have
thousands of packages in the tree that essentially do the same thing,
just with different API's. According to this philosophy, we should
change the name of the package every time net-misc/neon comes out with a
new version, since it breaks API on every version.

>>> For example, there are lots of packages requiring gtk1, other
>>> gtk2. As long as dependencies don't cope the slot cleanly, 
>>> slotting is utterly useless.
>> gtk-1 is deprecated, it will disappear sooner or later.
> 
> Maybe, maybe not. That will take some time until all packages are 
> rewritten from gtk1 to gtk2.
> 
> BTW: an "problem will go away by itself sooner or later" isn't 
> actually an good argumentation for such kind of problems.

There is no problem, gtk1 and gtk2 can be installed on the same system
at the same time, and all packages in the tree have their dependencies
set up to depends on whichever version of gtk they need. SLOTS take care
of this quite well.
-- 
gentoo-dev@gentoo.org mailing list

Reply via email to