Bug 8201 – gtk-engines should not be masked

• Product: Portage Development
• Status: VERIFIED FIXED

[Description Brian Mattern 2002-09-21 21:22:41 UTC]

gtk-engines seems to be accidentally masked, reportedly because of the move of
all the engines to gtk-engines-*, which doesn't make sense for this one. unless
the gtk2 engines are available elsewhere?

[Comment 1 foser (RETIRED) 2002-10-10 11:26:12 UTC]

Looks like you are right, unmasked gtk-engines. Thanks.

[Comment 2 Leonardo Boshell (RETIRED) 2002-11-10 23:12:38 UTC]

A note on thig bug: gtk-engines _should_ be masked. Please note that:

* Its functionality is now provided by several different packages. These are:

For gtk 1:
  gtk-engines-metal
  gtk-engines-notif
  gtk-engines-pixmap
  gtk-engines-raleigh
  gtk-engines-redmond95

For gtk 2:
  gtk-engines-metal
  gtk-engines-pixbuf
  gtk-engines-redmond95

* Gtk 1 engines has SLOT=1 and Gtk 2 engines has SLOT=2, so you can install them
without conflict

* 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*'

* The old gtk-engines-0.12 package included one more engine that isn't part of
the gtk-engines tarball. It is now available as gtk-engines-xenophilia too.


I hope it's clear now. Be aware that the old gtk themes-related packages will be
removed from the Portage tree soon. They're still there because we wanted to
test the new gtk-engines-* packages, and give everyone who still use the old
packages a chance to migrate cleanly.

So, gtk-engines is masked again.

[Comment 3 foser (RETIRED) 2002-11-11 07:50:14 UTC]

Hmm yeah, right. I even knew that, must've been asleep :/