See here:
This is probably an artifact of us including a copy of XPLC in the
distribution. It's debatable whether we should be depending on XPLC at all,
and if so, whether we should be including a local copy of it in our
distribution. Regardless, this is going to have to be fixed one way or another.
Original issue reported on code.google.com by wrl...@gmail.com on 4 May 2007 at 6:33
Original issue reported on code.google.com by
wrl...@gmail.com
on 4 May 2007 at 6:33