Christian Thalinger wrote: > On Wed, 2009-10-21 at 18:09 +0200, Raffaello Giulietti wrote: >> Hi Christian, >> >> I'm having troubles with mercurial's own mq extensions. >> >> I just installed OpenSolaris and extended it according to the general >> OpenJDK build instructions, then added mercurial and the forest >> extensions. But while the forest extensions work flawlessly (I could >> download da Vinci), the mq extensions do not, although they should come >> preinstalled. And yes, the flags are configured in the .hgrc file >> according to the build instructions of the mlvm (I tried both mq= and >> hgext.mq=). >> >> Did you (or anybody watching) encounter similar problems with >> mercurial/OpenSolaris.2009-06? > > No, never had problems with it. Do you have the mq.py file? > > twi...@macbook:~$ grep mq .hgrc > mq = > twi...@macbook:~$ ls -l /usr/lib/python2.4/vendor-packages/hgext/mq.py > -r--r--r-- 1 root bin 97773 2009-07-23 19:58 > /usr/lib/python2.4/vendor-packages/hgext/mq.py >
Yes, all mercurial py modules are there, installed by invoking pkg install SUNWmercurial. None of them, however, is accessed by hg. I suspect the installer fails to setup something in the environment to make python aware of the vendor-packages folder. _______________________________________________ mlvm-dev mailing list [email protected] http://mail.openjdk.java.net/mailman/listinfo/mlvm-dev
