On 8/7/06, Enrico Weigelt <[EMAIL PROTECTED]> wrote:
* Simon Stelling <[EMAIL PROTECTED]> schrieb:
> You've already been told it's a non-issue, but here's why:
>
> http://devmanual.gentoo.org/general-concepts/slotting/index.html
Oh hell, this can't be serious !
Yes it is and it's been in use for a Long Time Now(tm). It's not quite
perfect but at least it's usable.
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.
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 ?!
You might want to look at gcc, php, qt, apache and a couple of others
then. Dare I quote the devmanual :
"This is useful for libraries which may have changed interfaces
between versions — for example, the gtk+ package can install both
versions 1.2 and 2.6 in parallel."
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.
Ebuilds just have to depend upon =gtk-1.2* fex. Can I ask where did
you find a case where portage didn't handle it cleanly ? Also, file a
bug on it if possible ?
--
gentoo-dev@gentoo.org mailing list
