2009/3/30 Neil Bothwick <n...@digimed.co.uk>: > On Mon, 30 Mar 2009 08:24:54 +0200, Alan McKinnon wrote: > >> No. qt is now a meta package and exists only to have the qt split >> ebuilds as DEPENDencies, so it installs nothing. Unlike the kde split >> ebuilds, the devs decided not to call it qt-meta and promptly confused >> most of the KDE using community. > > I'd say that's a good thing, it saved having to change every ebuild > depending on qt to depend on || (qt qt-meta) and is the same way the > transition to split XOrg packages was handled. Te -meta addition to the > KDE package names was a necessary kludge, because the split builds lived > alongside the monolithic variants.
Calling it qt-meta instead of simply qt has nothing to do with this. No ebuild should ever depend on the qt meta ebuild, instead it should just depend on the needed parts that have been split up. So a transition from the single qt dependency to the split up parts was needed anyway and already took place. The only remaining reason for the meta ebuild is that some people who want all of qt can simply emerge the meta ebuild. -- Regards, Daniel
