Yeah, I see your point.

Hmm. Is it possible to store the installation information in the hg binary
itself? It's not a perfect solution, but it's a possible workaround. For
example, "hg --libraries" could list the associated libraries, and a
hypothetical "make uninstall" could run this command to determine what to do.

I would also argue that scanning ../lib/python would work if it is scanned
_before_ the system-wide directories such as /usr/[...]. It's unlikely that a
user would have old libraries in $HOME along with new binaries as these
libraries are Mercurial-specific. Of course, it may happen, and things would
break in that case.

It would certainly help if distributions would use a better standardized
directory structure!

Thanks,
Jacob