Collision with SystemTap on 'dtrace' binary (/usr/bin/dtrace vs /usr/sbin/dtrace)

[thesamesam]

Both SystemTap and DTrace install a dtrace binary. SystemTap does it at /usr/bin/dtrace for historical reasons as a wrapper, while DTrace installs it at /usr/sbin/dtrace.

While they're at two different paths, this is both:
a) confusing as it depends on order in PATH;
b) an actual collision on systems where /usr/bin == /usr/sbin (Gentoo does this on new systems, I believe Fedora is planning it, and so on)

On our side downstream in Gentoo, this is tracked as https://bugs.gentoo.org/938302.

This makes packaging DTrace difficult, and it also makes life hard for users who want to try both SystemTap and DTrace, as their target audience has a lot of intersection.

A solution needs to be worked out with the SystemTap folks on this. I suggest renaming the SystemTap wrapper to stap-dtrace with an optional compatibility dtrace -> stap-dtrace symlink on their side.

[thesamesam]

I'm happy to do some of the gruntwork in porting software for this. A lot of them really actually assume SystemTap anyway, they just call dtrace (its wrapper).