Comment 1 for bug 1745626

I'd be willing to consider any patches on this. I don't particularly like this either but people run the binary straight out of the virtualenv and get just as confused when it all breaks with weird tracebacks because it can't find the other binaries it needs. I remember at the time we looked around for other solutions, such as pkgutil but didn't really find anything that worked quite the same.

I think dib-run-parts is actually solved because we have diskimage_builder.paths.get_path('lib') where we run it from now. if there's some way we can know the canonical path to dib-block-device and others without this that would be good