On 2010-Feb-27 16:46, Luke wrote:
However, if the /path/to stuff really serves some purpose (as in: there are two ledgersmb13 directories? although how this would differentiate that, I don't know), I suppose it could stay. Still, the section title, and its extraneous slash, should change, imho.
It serves a purpose so long as there is no actual directory named "ledgersmb13". The "/path/to/" idiom is sufficient (at least for me) to make it clear that it refers to the top-level directory of the installed application.
My opinion is that anyone reading this document knows enough to include the appropriate above-ledgersmb13 path, or change directories to get above it, or whatever, in order to execute chown or chmod as needed. If not, they're probably using an automated install, and not reading the install doc for these details.
Or they're seeing the software for the first time (like me) and don't have the a priori knowledge of whether this refers to the install directory or if they're missing a subdirectory called "ledgersmb13". After all, there is a subdirectory called "LedgerSMB/", it's equally conceivable - for newbies - that it has the wrong name.
I was _reasonably_ certain, given the context, that the docs were only talking about the base install path itself, but from that angle - I'd say anyone reading this document probably already knows that apache needs to be able to read the files.
At least, I'm experienced enough to be using Gentoo (which is why I'm reading the docs): making sure the files are readable by Apache is almost a reflex action, didn't even need to be documented (for me), but I still wasn't sure which directory "ledgersmb13" referred to. I figured if it was important enough to mention specially like that, it must be something out of the ordinary. Until I found the other references to /path/to/ledgersmb13 which made it reasonably clear, anyway.
My $0.02. -- Thank you, -Adam Thompson <..hidden..> (204) 291-7950