Hi, I emerged xsv-2.7 but then couldn't find the xsv executable or the commandLine.py per usage recommendation from the tool's web page. Did I miss something here? After the emerge, I 'located' most xsv file in the portage tree under dev-python and /var/db/pkg/dev-python/xsv-2.7 but that's it. If the ebuild is like the source package installation described on their web site, then we are missing the 'commandLine.py' file I guess. Reproducible: Always Steps to Reproduce: 1. 2. 3.
The author of the XSV program recommends running it with >python commandLine.py but I didn't see that script anywhere in the Gentoo package. How do you guys run it?
I'm use python /usr/lib/python2.4/site-packages/XSV/commandLine.py to start it but it does not work: see bug #117130
i did some more analysis of this, actually the whole ltxml, pyltxml and xsv is broken. i tried to email the guys who work on ltxml and pyltxml with a patch that at least makes the latest version of pyltxml and ltxml compile, but they don't seem to be responding at all. i might commit what i have to at least make it compile, but i also cannot run the commandline xsv because it seg faults inside pyltxml. i suspect that we might have to remove ltxml, pyltxml and xsv from the tree because its not maintained upstream any more. otherwise, any suggestions?
(In reply to comment #3) > i did some more analysis of this, actually the whole ltxml, pyltxml and xsv is > broken. i tried to email the guys who work on ltxml and pyltxml with a patch > that at least makes the latest version of pyltxml and ltxml compile, but they > don't seem to be responding at all. > > i might commit what i have to at least make it compile, but i also cannot run > the commandline xsv because it seg faults inside pyltxml. > > i suspect that we might have to remove ltxml, pyltxml and xsv from the tree > because its not maintained upstream any more. otherwise, any suggestions? > Upstream guys were recommending using python2.3, so I removed ltxml,pyltxml and xsv, set the 'python' symlink to python2.3, re-emerged ltxml,pyltmxl and xsv, but I am still getting the segmentation fault as soon as I run python XSV/commandLine.py tiny.xml tiny.xsd I tried the same with the latest XSV-2.10.tar.gz, same thing. Did you try to contact henry thompson: ht at inf ed ac uk ? He's usually pretty responsive and I think he wrote ltxml, XSV and has a web version of XSV running somehow, so maybe he knows more.
This is way old, open a new bug if you still care.
