Ticket #5060 (closed defect: wontfix)
php view issue / freebsd port issue
| Reported by: | trac@… | Owned by: | jonas |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | wiki system | Version: | 0.10.3.1 |
| Severity: | normal | Keywords: | pygments |
| Cc: |
Description
I'm filing this with the trac wiki, and also with the freebsd port maintainer, as a fix could come from either.
i noticed an issue today when trying to look at a php file for the first time in trac - it wouldn't read at all. some googling and looking on the trac site made me realize that it was an issue with trac.ini , and the mimeviewer setting
the fix is easy: "php_path = php" -> "php_path= /usr/local/bin/php"
however this made me question 3 things:
1) why is php even involved in this at all? there is a ton of other syntax support in trac.
2) my old trac.ini install picked up the bin 'php', i tried a fresh install on a new machine, as well as speaking with friends who have run various versions on freebsd , centos , & ubuntu. all had a similar problem. is there a way that the system can better detect the php binary during ini writing? or maybe even try a few fallback locations if it just reads 'php' -- this seems to be a common issue.
3) i've been using trac since ~ the .7 branch and updating regularly. when i did a fresh install on a new box today , i realized much the ini files have been changing -- everything is still compatibile, but there are a ton of new settings. would it be possible to build into the trac distribution a sample trac.ini file per version from now on -- so people can diff the settings on any two trac versions ? i know that the ini is dynamically generated and not templated -- but if there were a way to just make a sample that comes with source, so when people update via ports/pkgs in various distros or from source, the info is all right there.
