On Tuesday 27 December 2005 04:08, Brian Harring wrote: > So note the comment in the email you are responding to about locking > down the used dep/rdeps for an install.
That would be a maintenance nightmare. Every time a new KDE versions comes out a new ebuild revision for every package depending on KDE would be needed to work with this particular KDE version. Just for the sake of having to match with insufficient slot dependencies. I'll give another example: Application X works with KDE 4.0 (which implies that it will work with all KDE 4.x versions). Locking the dependency down to e.g. kde-base/kdelibs:4.0 implies adding another ebuild revision depending on kde-base/kdelibs:4.1, another one on kde-base/kdelibs:4.2. In short: Even having slot dependencies they won't be used, because =kde-base/kdelibs-4* is the dependency, which matches and no one will add hundreds of ebuilds just to follow the limiting scope Portage is providing via slot dependencies. Based on the packages we have now in Portage, that would mean ~300 additional new ebuild revisions as a side effect of every KDE version bump. Simply ridiculous. Carsten
pgptdIP2KO63X.pgp
Description: PGP signature
