On Tuesday 27 December 2005 22:45, Carsten Lohrke wrote: > On Tuesday 27 December 2005 14:00, Jason Stubbs wrote: > > If all three of those packages were first built against kdelibs:3.4 and > > then kdelibs:3.5 became available then rebuilding any one of them without > > rebuilding the others will break digikam. I can't see how it's directly > > represented in the metadata unless you want to overload the meaning of > > SLOT. > > It's not possible to represent that via dependencies. What is needed is > some sort of introspection which relevant ebuild is built against which KDE > version and if those _installed_ ebuild:kdever combinations match the one > the _actual_ ebuild to emerge.
Do you mind reading and replying to the second paragraph (which happens to be the only new information I brought to this thread). Underlining words to emphasize a point to me that I've opened by agreeing is really not necessary. > But you're right about the overloading of the meaning of slots, because > that's happening right now. Slots are used to install several versions of a > package side by side. The idea Ciaranm and Brian are proposing to lock > ebuilds depending on slotted packages down to a single slot is the > redefinition. And once again: This doesn't match reality. You've misunderstand what is meant by "locking ebuild dependencies". I gave you a definition in my second paragraph. Please have a re-read. -- Jason Stubbs -- gentoo-dev@gentoo.org mailing list
