We use fossil on Windows for several ongoing customer projects and are
quite pleased. Out of long-standing habits born of too many years
dealing with command-line tools, we are fairly careful to keep spaces
out of path and file names inside repositories. However, I have several
cases where the repositories themselves are stored in locations with
spaces in their path names, and that has only caused one problem that I
just noticed today.
Specifically, we use an Apache installation on one of our less-occupied
PCs to host "master" copies of all the project repositories. This
provides for easy access to their tickets and timelines from the web ui,
and allows the working copies on our various development machines to
have a "remote" repository to sync to that is always available despite
some developers connecting only occasionally by VPN.
Apache is configured with a simple CGI script to pass requests through
to fossil for any and all *.fossil files in a single folder. When we
moved the folder on the hosting PCs file system to a location that
included spaces in the name, fossil cgi stopped being able to locate any
of the repositories. Changing the path names to no longer include spaces
fixed the issue.
In other words, the file /cgi-bin/repo works if it looks like this:
#!fossil
directory: C:/Some-Place-Sensible/Repositories/Fossil
notfound: http://example/cgi-bin/repo/main
But failed when it looked like this:
> #!fossil
> directory: C:/Some Place Sensible/Repositories/Fossil
> notfound: http://example/cgi-bin/repo/main
I did try various kinds of quoting that seemed plausible with no joy.
Changing the name to not have spaces made sense for lots of reasons, so
we are content with that work-around.
Fossil itself reads that file as the CGI handler, and I don't know if if
does have a quoting mechanism for path names in the CGI script, or even
if it should have one.
I imagine that using any non-ASCII characters in the path name could
also have caused "interesting" behavior, but I haven't tried that.
On 6/11/2012 3:36 PM, Mike Meyer wrote:
....
His problem is that he has lots of spaces in his directory and file
names, and we (Windows is a third-line gaming platform for me, but I
try...) couldn't figure out how to get such passed to fossil as file
names, instead of broken up by command.com or whatever does that job
these days. Quoting again:
....
--
Ross Berteig [email protected]
Cheshire Engineering Corp. http://www.CheshireEng.com/
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
