Re: [gentoo-user] qt-4.4.3 won't install any files
On Mon, 30 Mar 2009 14:58:43 +0200, Daniel Pielmeier wrote: > > OK, so the meta ebuild is just a safety net for those running ebuilds > > not in the portage tree. > Probably, but even overlays should consider changing the dependencies > and use the advantage of the split ebuilds ;-) Absolutely, but should != do :( -- Neil Bothwick Pound for pound, the amoeba is the most vicious animal on the earth. signature.asc Description: PGP signature
Re: [gentoo-user] qt-4.4.3 won't install any files
2009/3/30 Neil Bothwick : > On Mon, 30 Mar 2009 14:17:00 +0200, Daniel Pielmeier wrote: > >> > So every ebuild, in the tree and all overlays, was updated before the >> > split ebuilds were introduced? > >> I don't know the exact progress but I think the split ebuilds were >> introduced masked, then the dependencies have been adjusted >> accordingly. After the transition was done the ebuilds have been >> unmasked. > > OK, so the meta ebuild is just a safety net for those running ebuilds not > in the portage tree. > Probably, but even overlays should consider changing the dependencies and use the advantage of the split ebuilds ;-) -- Regards, Daniel
Re: [gentoo-user] qt-4.4.3 won't install any files
On Mon, 30 Mar 2009 14:17:00 +0200, Daniel Pielmeier wrote: > > So every ebuild, in the tree and all overlays, was updated before the > > split ebuilds were introduced? > I don't know the exact progress but I think the split ebuilds were > introduced masked, then the dependencies have been adjusted > accordingly. After the transition was done the ebuilds have been > unmasked. OK, so the meta ebuild is just a safety net for those running ebuilds not in the portage tree. -- Neil Bothwick All things in moderation, ESPECIALLY moderation. signature.asc Description: PGP signature
Re: [gentoo-user] qt-4.4.3 won't install any files
2009/3/30 Neil Bothwick : > On Mon, 30 Mar 2009 12:53:30 +0200, Daniel Pielmeier wrote: > >> So as far as I see the new qt meta ebuild wasn't needed at any time. > > So every ebuild, in the tree and all overlays, was updated before the > split ebuilds were introduced? > I don't know the exact progress but I think the split ebuilds were introduced masked, then the dependencies have been adjusted accordingly. After the transition was done the ebuilds have been unmasked. -- Regards, Daniel
Re: [gentoo-user] qt-4.4.3 won't install any files
On Mon, 30 Mar 2009 12:53:30 +0200, Daniel Pielmeier wrote: > So as far as I see the new qt meta ebuild wasn't needed at any time. So every ebuild, in the tree and all overlays, was updated before the split ebuilds were introduced? -- Neil Bothwick You cannot really appreciate Dilbert unless you've read it in the original Klingon. signature.asc Description: PGP signature
Re: [gentoo-user] qt-4.4.3 won't install any files
2009/3/30 Neil Bothwick : > On Mon, 30 Mar 2009 10:38:48 +0200, Daniel Pielmeier wrote: > >> 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. > > During the transition, there will be lots of packages depending on qt. > Your argument becomes true when all previous qt:4 ebuilds vanish from the > tree, and so do all ebuilds depending on them. Until then, the meta ebuild > is required, as it was with XOrg. > Okay, let me try to make this more clear. First some example dependencies for the switch from monolithic to split qt which happened between qt-4.3 and qt-4.4: monolithic phase: DEPEND="x11-libs/qt:4" transition phase (monolithic and split qt coexist): DEPEND="|| ( ( x11-libs/qt-gui x11-libs/qt-opengl ) =x11-libs/qt-4.3* )" split phase (only split qt left): DEPEND="x11-libs/qt-gui x11-libs/qt-opengl" In the monolithic phase there was no meta ebuild and everything depended on the monolithic qt ebuild. During the transition phase the dependencies have been separated to make it possible to use either the monolithic qt-4.3 or the split qt-4.4 without any ebuild depending direct on the new qt-4.4 meta ebuild but just the split parts which are needed by the application. After the removal of the monolithic qt-4.3 ebuild which already happened the ebuilds need to depend on the split parts only. So there should be no ebuild in the monolithic phase and almost all ebuilds in the transition phase that will be slowly converted to the split phase. So as far as I see the new qt meta ebuild wasn't needed at any time. -- Regards, Daniel
Re: [gentoo-user] qt-4.4.3 won't install any files
On Mon, 30 Mar 2009 10:38:48 +0200, Daniel Pielmeier wrote: > 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. During the transition, there will be lots of packages depending on qt. Your argument becomes true when all previous qt:4 ebuilds vanish from the tree, and so do all ebuilds depending on them. Until then, the meta ebuild is required, as it was with XOrg. -- Neil Bothwick Top Oxymorons Number 45: Resident alien signature.asc Description: PGP signature
Re: [gentoo-user] qt-4.4.3 won't install any files
Thankyou guys Francisco
Re: [gentoo-user] qt-4.4.3 won't install any files
2009/3/30 Neil Bothwick : > 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
Re: [gentoo-user] qt-4.4.3 won't install any files
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. -- Neil Bothwick Committee (noun): A group of people spending hours taking minutes signature.asc Description: PGP signature
Re: [gentoo-user] qt-4.4.3 won't install any files
On Monday 30 March 2009 08:13:33 Francisco Ares wrote: > I have qt-3.3.8b-r1 and qt-4.4.2 > > I tried qt-assistant-4.4.2-r1, and it showed me no docs. [snip] > Nothing showing the traditional compile and install procedure. Is this a > bug? 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. What you should do, it grep your world file for 'qt' and delete all explicit references therein to qt ebuilds. The 'emerge avuND world' and let portage figure out which ones you need based on dependencies of stuff that uses it. If 'emerge --depclean' wants to remove you want to keep, then you can add that back to world explicitly -- alan dot mckinnon at gmail dot com
