Trunk of Trac seems to work fine with trunk of Genshi. Why do I need to use 
branches/experimental/advanced-i18n?

Regards,
Volker

-- 
Dipl.-Inform. Volker Kamin

RWTH Aachen University
Embedded Software Laboratory
Ahornstr. 55
52074 Aachen

fon: +49 241 80 21157
fax: +49 241 80 22150
web: http://www.embedded.rwth-aachen.de/


-----Ursprüngliche Nachricht-----
Von: [email protected] [mailto:[email protected]] Im 
Auftrag von Remy Blank
Gesendet: Dienstag, 27. Oktober 2009 20:02
An: [email protected]
Betreff: [Trac] Re: Which 0.12dev to use

Kamin, Volker wrote:
> Is there a revision of 0.12dev that you believe to be "more stable" 
> than others?

trunk is usually "fairly stable", but there's of course no guarantee for any 
revision. OTOH, if you install from SVN, and a particular revision gives you 
trouble, it's pretty easy to update to a more recent version.

> The same question goes for genshi.

If you use trunk, you must install the advanced-i18n branch of Genshi:

http://svn.edgewall.org/repos/genshi/branches/experimental/advanced-i18n

> Also: mod_python seems to be dead and it limits us to Python 2.5. Is 
> WSGI working properly by now?

WSGI is actually the recommended way to run Trac.

> mySQL 5.1 is also available: is it better to use mySQL or sqlite?

This depends on the number of users, and how often they use Trac. For small 
installations (~50 users), SQLite is more than adequate. If you have more 
users, I would suggest using PostgreSQL. While MySQL works and is officially 
supported, it has a few drawbacks (you can read about them on the MySQL page on 
trac.edgewall.org) and not that many users.

Good luck!

-- Remy


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected]
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to