[Trac] Re: [Q] installing Subversion SWIG bindings in a virtualenv?
Olaf Meeuwissen wrote: > Noah Kantrowitz <[EMAIL PROTECTED]> writes: > >> Olaf Meeuwissen wrote: >>> Hi all, >>> >>> I've been looking into setting up a server with multiple Trac envs, >>> using a combination of virtualenv and WSGI to keep the environments >>> separate. As I'd also like to keep the server's Python environment >>> separate from that used by the Trac environments, I created another >>> `virtualenv --no-site-packages` and used that for WSGIPythonHome. >>> To this WSGIPythonHome virtualenv you can easy_install whatever you >>> need for all the Trac environments. >>> >>> I got that to work fine as long as you don't have a Trac environment >>> that uses a Subversion repository. Trac requires the Subversion SWIG >>> binding (as opposed to PySVN which is just an easy_install away) and >>> I have no clue how to install that (short of `make swig-py; sudo make >>> install-swig-py`, which is a no-go on a production machine). >>> >>> Is there an easy way to install the Subversion SWIG bindings in a >>> virtualenv, or two? >> Subversion installs the bindings to $PREFIX/lib[64]/svn-python/ so if >> you set $PREFIX to be some temp folder, and then move the svn/ and >> libsvn/ folders into the virtualenv site-packages it should work fine. > > Eh, I think I also need the various *.py files, correct? > > I had a look at the content of Debian's python-subversion package and > it looks like I can use that as is by just doing a `dpkg-deb -x` in > the right place. > ... me goes off to give that a try ... > Tough luck. I couldn't get that to work. > > Resyncing from within a virtualenv gives: > > Command failed: Unsupported version control system "svn": "No module named > _fs" > > Apparently some of the search paths are missing bits and pieces. > > At least the all the *.(so|py) files in python-subversion do not seem > to refer to absolute filenames. So am under the impression that Noah > is right and the $PREFIX approach should work fine but I do not have > the time to test that right now :-( > > Any other suggestions? Given that the gentoo install process does exactly what I said, this works fine. Do not try to move just certain files, move those two entire folders as is. --Noah signature.asc Description: OpenPGP digital signature
[Trac] Re: [Q] installing Subversion SWIG bindings in a virtualenv?
Noah Kantrowitz <[EMAIL PROTECTED]> writes: > Olaf Meeuwissen wrote: >> Hi all, >> >> I've been looking into setting up a server with multiple Trac envs, >> using a combination of virtualenv and WSGI to keep the environments >> separate. As I'd also like to keep the server's Python environment >> separate from that used by the Trac environments, I created another >> `virtualenv --no-site-packages` and used that for WSGIPythonHome. >> To this WSGIPythonHome virtualenv you can easy_install whatever you >> need for all the Trac environments. >> >> I got that to work fine as long as you don't have a Trac environment >> that uses a Subversion repository. Trac requires the Subversion SWIG >> binding (as opposed to PySVN which is just an easy_install away) and >> I have no clue how to install that (short of `make swig-py; sudo make >> install-swig-py`, which is a no-go on a production machine). >> >> Is there an easy way to install the Subversion SWIG bindings in a >> virtualenv, or two? > > Subversion installs the bindings to $PREFIX/lib[64]/svn-python/ so if > you set $PREFIX to be some temp folder, and then move the svn/ and > libsvn/ folders into the virtualenv site-packages it should work fine. Eh, I think I also need the various *.py files, correct? I had a look at the content of Debian's python-subversion package and it looks like I can use that as is by just doing a `dpkg-deb -x` in the right place. ... me goes off to give that a try ... Tough luck. I couldn't get that to work. Resyncing from within a virtualenv gives: Command failed: Unsupported version control system "svn": "No module named _fs" Apparently some of the search paths are missing bits and pieces. At least the all the *.(so|py) files in python-subversion do not seem to refer to absolute filenames. So am under the impression that Noah is right and the $PREFIX approach should work fine but I do not have the time to test that right now :-( Any other suggestions? -- Olaf Meeuwissen FLOSS Engineer -- AVASYS Corporation FSF Associate Member #1962 sign up at http://member.fsf.org/ --~--~-~--~~~---~--~~ You received this message because you are subscribed to the Google Groups "Trac Users" group. To post to this group, send email to trac-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/trac-users?hl=en -~--~~~~--~~--~--~---
[Trac] Re: [Q] installing Subversion SWIG bindings in a virtualenv?
Olaf Meeuwissen wrote: > Hi all, > > I've been looking into setting up a server with multiple Trac envs, > using a combination of virtualenv and WSGI to keep the environments > separate. As I'd also like to keep the server's Python environment > separate from that used by the Trac environments, I created another > `virtualenv --no-site-packages` and used that for WSGIPythonHome. > To this WSGIPythonHome virtualenv you can easy_install whatever you > need for all the Trac environments. > > I got that to work fine as long as you don't have a Trac environment > that uses a Subversion repository. Trac requires the Subversion SWIG > binding (as opposed to PySVN which is just an easy_install away) and > I have no clue how to install that (short of `make swig-py; sudo make > install-swig-py`, which is a no-go on a production machine). > > Is there an easy way to install the Subversion SWIG bindings in a > virtualenv, or two? Subversion installs the bindings to $PREFIX/lib[64]/svn-python/ so if you set $PREFIX to be some temp folder, and then move the svn/ and libsvn/ folders into the virtualenv site-packages it should work fine. --Noah signature.asc Description: OpenPGP digital signature
