The Nero linux ebuild have some useless deps: Nero linux 2.0 depend on libX11 or virtual/x11 AND gtk+1-2. gtk+-1.2 depend on libXi (that depend on libX11) or virtual/x11. So the Nero linux dep on libX11 || virtual/x11. Even the sys-libs/glibc dep seems redundancy to me. Reproducible: Always Steps to Reproduce: 1.cat /usr/portage/app-cdr/nero/nero-2.1.0.3.ebuild 2.cat /usr/portage/x11-libs/gtk+/gtk+-1.2.10-r12.ebuild 3.cat /usr/portage/x11-libs/libXi/libXi-1.1.0.ebuild Actual Results: Useless dependency. Expected Results: Just one dependency.
It needs to be bumped for new version which uses GTK+-2.0 anyway.
(In reply to comment #1) > It needs to be bumped for new version which uses GTK+-2.0 anyway. > Hm, old Nero serials don't work with the new version (3.*), so if Nero keeps shipping updates (they seem to do that), why shouldn't it stay in the tree? (It sounded like you suggested that it should be removed from the tree anyway.)
> It needs to be bumped for new version which uses GTK+-2.0 anyway. Yes, but on the bug for the 3.0.0.0 someone suggest me to warn about the trivial bug. And I think that is a good idea. :)
(In reply to comment #2) > why shouldn't it stay in the tree? GTK+ 1.2.* is highly deprecated and should be avoided.
*** This bug has been marked as a duplicate of bug 176024 ***
Plus, relying on indirect deps is completely evil.
> Plus, relying on indirect deps is completely evil. So is correct to have in any package the glibc dependency? Or in any package that use the GTK+ the x11 dependency? I think that indirect deps is *THE* way. :) However I didn't understand why you put the new version of nero-2 as duplicate of this bug.
(In reply to comment #7) > I think that indirect deps is *THE* way. :) That's just wrong. How are you going to track them? Are you going to watch all the ebuilds that pull in the indirect deps and re-add the dependency if they drop it? Good luck with this. Ebuilds should state *all* the deps they need (minus implicit system dependencies guaranteed to be present on every system that the ebuild is keyworded for). > However I didn't understand why you put the new version of nero-2 as duplicate > of this bug. Because this gtk1 stuff will leave the tree as soon as something decent gets committed.