echo $HOME/lib/svn-python > $HOME/lib/python2.3/site-packages/subversion.pth
I have no idea why this is required and I think it worked without it, but the Subversion SWIG Install instructions say that you need to do. It gave the reason, but it was too confusing for me to understand so I couldn't remember what the text said. I don't feel like going back to read it.
If you know or understand the reason behind this then you could tell me and write the reason in the guide? Thanks.
Santosj 07:43, 25 Feb 2006 (PST)
This is required to use the Subversion Python SWIG bindings, e.g. Trac. There are other ways to go about this, but this is probably the easiest way that I've seen. By default, subversion installs the bindings in the first directory where python doesn't know to look for it. This command makes python aware of the bindings.
Ascarid68 14:11, 22 Apr 2006 (PDT)
- Thanks for clearing that up! It could be the source of a some people having problems. Santosj 07:02, 23 Apr 2006 (PDT)
I don't have a libsvn in .../lib/python2.3/site-packages/
So I can't do this:
cd $HOME/lib/python2.3/site-packages mv libsvn libsvn.b0rk
--Marlun 07:29, 15 Mar 2006 (PST)
- If you don't have it then you don't need to do it. It is just there in case you have the folder and stuff in it. If you don't have the folder then the symbolic links will take care of the rest. Santosj 14:56, 16 Mar 2006 (PST)
I never created those symbolic links and my Trac installation still seems to work, what do they do? Should I create them now anyway? --Marlun 15:45, 16 Mar 2006 (PST)
- No, if it works then it is all good. It was a fix for an issue a long time ago for I think SWIG/Subversion Bindings. It is good to cover all bases in case someone does have an issue, at least they would have it fixed. -Santosj 19:33, 16 Mar 2006 (PST)
I followed the various MySQL installations with success for a single project repository.
As I have multiple SVN repositories at svn.hostname.dom/*, I'd like to have multiple Trac projects at trac.hostname.dom/*. I was able to do it by modifying the index.f?cgi. Commenting out the line containing "export TRAC_ENV=", and adding:
However, the linking (most obviously CSS resources) get all messed up with the pretty modifications. For example,
http://trac.domainname.dom/repos/chrome/common/css/trac.css exists (after the .htaccess RewriteRule), but the pages try to find: http://trac.domainname.dom/index.fcgi/chrome/common/css/trac.css or something of the like.
Anyway, my acceptable work around is as follows (from the begining). I've created a new subdomain and database name for each project/repository using a single databases server/domain and user. For each subdomain, I point to the trac_sites/repos as in the documentation above. aeg 3 Apr 2007
Run the configuration script
you must first: cd subversion-x.x.x