Summary: | gtk-engines metapackage strongly desired | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | synonymousca |
Component: | New packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED WONTFIX | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
synonymousca
2003-01-26 07:07:04 UTC
I'm afraid I don't understand you very well. You don't need to 'emerge /usr/portage/x11-themes/gtk-engines*/g*.ebuild', nor "delete the ebuilds for irrelevent versions". If you read the comments on bug #8201, you can find the following: There is a convenient package which install all the proper engines you might want: gtk-themes. If you want Gtk 2 themes you can just 'emerge gtk-themes'. However, if you want Gtk 1 themes, you can 'emerge =gtk-themes-1.0*' As far as I can tell, once you upgraded to Gnome 2, all you had to do to is ``emerge gtk-themes'' and that's all there is to it. gtk-themes _is_ the meta-package in this case. Did I misunderstand you? You've misunderstood me somewhat. I already had most of the theme engines installed. I needed (in order to eliminate annoying console error messages) to recompile several of them, and I figured I might as well do the whole batch. As the engines were already installed, remerging gtk-themes without the --emptytree option would do nothing for me. Using the --emptytree option, on the other hand, would rebuild dozens of packages needlessly. What I'm really protesting is that the gtk-engines package (distributed by GNOME) has been broken up into about ten separate ebuilds (which is fine as an option, I guess, for those people who really feel a need to save 400 kb of disk space) and that the one big package which handled them all is gone. If you want/need to remerge them (same versions as are already installed), this means ten packages must be rebuilt rather than one. the last gtk+ ebuild containts a simple line at then end to rebuild your installed theme engines. btw leonardp, i dont have much dealings with engines, but shouldnt they be updated sinec the new gtk-engines pack is out and i see some themes are b0rked here and i suspect it has todo with engines being too old ? reporter : in time it doesnt matter if you compile one big pack or several smaller ones, so i don't really see that point. And i don't think its broken up for diskspace, but for conformation between the engines. foser: So it does. I must have missed that thanks to that little problem called 'merging multiple packages at a time' (And yes, I know of and can't be bothered to use the workaround mentioned in aone of the newsletters.) The dig about disk space was more of a joke than anything - I don't think it was necessary to split them out in the first place. Either way, feel free to close this bug unless you want it open as an 'update gtk-engines' reminder. im closing this, i don't really think its a good idea to have a gtk-engines package while there are several gtk-engines-* packages around. Too confusing, packages depending on gtk-engines should just depend on the seperate engines contained in the pack like the newest gnome-themes ebuild. |