On Thu, 2005-01-27 at 10:04 +0900, Georgi Georgiev wrote: > > After a fresh rsync on a sort-of fresh system: > > livecd ~ # emerge -pvt gtk-engines > > These are the packages that I would merge, in reverse order: > However, I don't want to have gtk+-1.2 installed for no reason at all. > As you can see, it is not installed already, and yet, according to > the gtk-engines ebuild: > > [ -n "${HAS_GTK1}" ] && DEPEND="${DEPEND} >=media-libs/imlib-1.8" > > These are the packages that I would merge, in reverse order: > > Calculating dependencies QA Notice: has_version() in global scope: eclass > gtk-engines2 > QA Notice: has_version() in global scope: eclass gtk-engines2 > QA Notice: has_version() in global scope: eclass gtk-engines2 > QA Notice: sed in global scope: x11-themes/gtk-engines-2.2.0 > ...done! > [ebuild N ] x11-themes/gtk-engines-2.2.0 0 kB > > The gtk-engines2.eclass has a has_version and then sets the HAS_GTK1 > variable. This has come up before many times, but is there something in > the works that solves this kind of problem? Is this a bug in the eclass, > since the message "QA Notice: has_version() in global scope:" sounds > like it is a Bad Thingâ and has to be avoided? More use flags maybe? > gtk2only, gtk1 or anything to stop this madness? Preventing metadata > from being generated for ebuilds that generate "QA Notice"s? >
See bug http://bugs.gentoo.org/show_bug.cgi?id=24439 as well as the gentoo-desktop mailing list archives. -- Mike Gardiner (Obz) ------------------- irc.freenode.org/#gentoo-dev #gentoo-desktop [EMAIL PROTECTED] http://www.gentoo.org
signature.asc
Description: This is a digitally signed message part