Trac 配置为访问 Perforce 存储库？
有人成功使用 TRAC 票务 + wiki 系统访问 Perforce 存储库中的代码库吗？
我浏览了 TRAC 相关网站，发现了这个一个，但最新的更改是该页面大约是一年前的样子，所以我得出的结论（如果我错了，请纠正我）该插件很难处于工作状态，或者由于某种原因最近没有任何进展。
Have someone used with success TRAC ticketing + wiki system accessing a code base residing in Perforce repository?
I've browsed in the TRAC related web sites and found this one, but the latest change on the page is something like an year ago, so I have concluded (correct me if I'm wrong) that the plugin is hardly in working state OR that for some reason there is no recent developments.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
我们将 Trac 与 Perforce 结合使用，基于您已经提到的 PerforcePlugin。我们已经使用该组合大约 1.5 年了。
该插件对于日常工作来说基本上足够稳定，但是如果使用大型存储库，请准备好摆弄服务器内存分配并要有耐心。此外，它还有一些令人恼火的错误，正如您已经注意到的那样，开发似乎完全停滞了。公平地说，必须说一些错误是由于 Trac 行为的缺陷以及与“Perforce Way”的不兼容造成的。
我会再次使用 Perforce 安装 Trac 吗？可能不会。如果强制使用Perforce，我会考虑Redmine + Perforce。
We are using Trac with Perforce, based on the PerforcePlugin you already mentioned. We have used the combination for about 1.5 years.
The plugin is basically stable enough for day-to-day work, but be prepared to fiddle with server memory allocation and have patience if working with large repositories. Also, it has some irritating bugs, and as you have already noticed, development seems to have stalled completely. In fairness it must be said that some of the bugs are due to shortcomings in Trac behaviuor and incompatability with "The Perforce Way".
Would I install Trac with Perforce again? Probably not. If forced to use Perforce, I would consider Redmine + Perforce.
在 Trac-hacks 上还需要注意的一点是插件开放票证的数量和内容。 PerforcePlugin 有很多开放票。
Something else to watch out for on Trac-hacks is the quantity and content of the open tickets for the plug-in. The PerforcePlugin has a lot of open tickets.
此更新可能会对您有所帮助：http://lynxline.com/tracperforce/，人们可以使用 Trac 正常工作1.0
This update may help you: http://lynxline.com/tracperforce/, people got it working okay with Trac 1.0