Bug 37526 – calltree ebuild has hardwired dependancy on valgrind 2.0.0

• Status: RESOLVED INVALID
• Product: Gentoo Linux

[Description narendra sankar 2004-01-07 14:16:49 UTC]

calltree is needed by Kcachegrind. The current ebuild is hardwired via 
the DEPEND="=dev-util/valgrind-2.0.0" and causes the valgrind ebuild to ping
pong between versions 2.0.0 and 2.1.0 on every world update. This depend
should be changed to DEPEND=">=dev-util/valgrind-2.0.0".


Reproducible: Always
Steps to Reproduce:
1.
2.
3.

[Comment 1 Paul de Vrieze (RETIRED) 2004-01-08 06:02:37 UTC]

This version of calltree (the newest actually) does not support valgrind-2.1.0 and fails in the configure script when using emerge with --nodeps, so the DEPEND is correct.

Actually the interface changed between valgrind-2.0.0 and valgrind-2.1.0 so even binary calltree does not work.

[Comment 2 Paul de Vrieze (RETIRED) 2004-01-08 06:07:09 UTC]

So this bug is invalid

[Comment 3 narendra sankar 2004-01-08 09:20:21 UTC]

If Calltree does not work with Valgrind 2.1.0, then shouldn't there be a block on upgrading from Valgrind 2.0.0 to Valgrind 2.1.0. The current behavior is a world update ping pongs between the two valgrind versions. That does not seem to be correct behavior. Should this be a calltree ebuild bug or a Valgrind ebuild bug?

[Comment 4 Paul de Vrieze (RETIRED) 2004-01-08 11:52:28 UTC]

It is a known missing feature in portage. The easiest workaround is to make sure that valgrind is not in your world file. That will prevent the flipping