On 30/08/12 00:46, Michal Suchanek wrote:
On 29 August 2012 13:20, Stephan Beal <[email protected]> wrote:
On Wed, Aug 29, 2012 at 12:15 PM, Stuart Rackham <[email protected]> wrote:
Yes, the "allow-symlinks" setting is on, in this particular repository
there are shared resources (CSS files and images) that are common to
...a symlink and load the actual file artifact that it refered to. This
is what you expect when you read a file via a symlink and is how a web
server would treat the file if it resided on a file system.
That is a reasonable/realistic assumption, but symlinks support was grafted
on much later and almost certainly has a corner case or three remaining
(symlinks aren't platform-portable, and were not originally supported at all
by fossil).
Aside from not being platform-portable following symlinks also
requires checking if they point outside of the checkout tree or not.
The alternative - using proper relative references to the files in
another directory resolves the symlinks in the browser which is
portable and can only work for files that shall be accessible.
Moving the project to Fossil was an after-thought (I had previously
looked at Fossil but discounted it at the time due to lack of symlink
support). I guess if Fossil was a project requirement right at the
start I would have considered this approach, but in any case the use
of symlink indirection is nice as it removes resource location
dependency from the HTML documents in the various document
directories.
Cheers, Stuart
Thanks
Michal
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
