They are currently on the first beta of 0.11. We should have a masked ebuild for it.
Added trac_0.11_beta1 to CVS, please test and report here.
worked for me on amd64. only issue is some plugins didn't work, but that's to be expected with a beta release
(In reply to comment #1) > Added trac_0.11_beta1 to CVS, please test and report here. > Dunno how its working for other people. But for me, the directory locations are all wrong. /usr/share/webapps/trac/0.11_beta1/htdocs has nothing inside it. Here are some of the differences on where the files end up between 0.10.4 and 0.11_beta1: 0.10.4 ====== htdocs -> /usr/share/webapps/trac/0.10.4/htdocs templates -> /usr/share/trac/templates wiki -> /usr/share/trac/wiki-default 0.11_beta1 ========== htdocs -> /usr/lib/python2.5/site-packages/trac/htdocs template -> /usr/lib/python2.5/site-packages/trac/templates wiki -> /usr/lib/python2.5/site-packages/trac/wiki Something's gone wrong. Care to comment?
everything works fine for me, but I don't use webapp-config or whatever it is, I manually set up each webapp myself.
(In reply to comment #4) > everything works fine for me, but I don't use webapp-config or whatever it is, > I manually set up each webapp myself. > Are you saying your /usr/share/webapps/trac/0.11_beta1/ directory has credible contents? Here are my contents: ./htdocs ./hostroot ./hostroot/cgi-bin ./hostroot/icons ./hostroot/error ./sqlscripts ./hooks ./conf ./postinst-en.txt ./postupgrade-en.txt ./installed_by_webapp_eclass As you can see it is pretty sparse. If I had something credible in the above directory I would try installing it where ever I wanted.
nope, pretty much empty. but here's my config in my ssl web root I have a symlink to: trac -> /usr/share/webapps/trac/0.11_beta1/htdocs/ my ssl vhost conf then has this: <location /trac> SetHandler mod_python PythonInterpreter main_interpreter PythonHandler trac.web.modpython_frontend PythonOption TracEnvParentDir /var/lib/trac/ PythonOption TracUriRoot /trac SetEnv HTTPS 1 </Location> <LocationMatch "/trac/[^/]+/login"> AuthType Basic AuthPAM_Enabled on AuthPAM_FallThrough on AuthBasicAuthoritative off AuthName "AuthHere.example" Require valid-user SetEnv HTTPS 1 </LocationMatch> Everything works, so I'd say you don't need anything there. the symlink probably isn't even needed
(In reply to comment #6) > nope, pretty much empty. but here's my config > > [..snip..] > I guess, don't knock it until you try it. It *does* work. However, as I said earlier in comment 3, I feel a little bit icky about all of my htdocs, templates and wiki files end up inside /usr/lib/python2.5/site-packages/trac. Surely that's now how webapp-config is intended to work? Julien?
(In reply to comment #7) > However, as I said earlier in comment 3, I feel a little bit icky about all of > my htdocs, templates and wiki files end up inside > /usr/lib/python2.5/site-packages/trac. Surely that's now how webapp-config is > intended to work? Julien? > This is how trac-0.11 is intended to work, that is, serving htdocs through the python handler. Symlinking should not be needed. Although, for performance reasons (CGI use for example), you might want to access directly to static resources. See http://trac.edgewall.org/wiki/TracCgi#MappingStaticResources for further information. Webapp-config is only useful when USE +cgi and/or +fastcgi, because trac.cgi and/or trac.fcgi have to be copied into every web root.
