Totem 0.99.19 and above require libnautilus-burn, even for its gtk-only build. This library is provided by the package nautilus-cd-burner. That package in turn requires libnautilus-extension, provided by the package nautilus. However, the users who want a gtk-only build will probably not want to install the nautilus application and its gazillion GNOME library dependencies. Therefore, I think there should be separate ebuilds for libnautilus-extension and libnautilus-burn in order to allow users to install a gtk-only totem. Reproducible: Always Steps to Reproduce: 1. 2. 3.
then don't build gtk only, it is not even enabled because it's broken in .19, so i dunno what you are on about. And even if it did it would still be a thoughtless request, because nautilus-burn requires nautilus-extensions which requires still nautilus & eel & a lot of other gnome deps. this is _NOT_ a blocker or even major.
Hadess, the maintainer of totem, encouraged me to report this because, as he says, distros should be packaging these separately. Fedora already does. So don't be criticizing me when a lead programmer says he app won't even be usable on our distro until we change things first. Hadess says that one can compile certain nautilus things without the GNOME stuff. In fact, libnautilus-burn links with only glib, gtk+, and libnautilus extensions. Maybe you should talk to him.
hadess is used to rpm based distros, those split binaries up because their package management is unusable otherwise. We normally don't do so and this is certainly no reason to start doing it here. Plus the fact that nautilus-extension alone requires 4 major gnome libs (check it), pretty much defeating the whole purpose of splitting it up. Sure you /can/ do a lot of hacks, if it's feasible distro-wise is another. Actually i already mentioned to hadess the gtk-only build was broken & the nautilus dep made the option pretty pointless long before this bug got posted.
