Hi guys, I am just getting started with Fossil again, after a brief fling back in late 2009. I was very impressed, but my project has lots of symlinks, which is what brought me to a halt before.
When I created my "woof2" repository, I ticked "allow-symlinks". All seemed well, however when I did a test clone of the repository, symlinks were turned off, so when I did "fossil open" all I got were files, not symlinks. So, I thought, perhaps I need to put .fossil-settings/allow-symlinks (with content "on") into the repository: # fossil add --dotfiles .fossil-settings I pushed that, then cloned, nup still no symlinks. Bye the way, does it cause any conflict have .fossil-settings in the repository? So then I thought of creating .fossil-settings/allow-symlinks after cloning and just before running "fossil open ../woof2.fossil". Still no go. So, finally, this worked: # fossil clone --admin-user MrSmith http://bkhome.org/fossil/woof2.cgi woof2.fossil # fossil ui woof2.fossil ...go to 'Admin/Settings' and tick "allow-symlinks" checkbox, then click "Apply Changes" button. close web browser, ctrl-c to kill "fossil ui" # mkdir woof2 # cd woof2 # fossil open ../woof2.fossil My question is, if I have 'allow-symlinks' in the online repository, shouldn't the clone operation inherit that? To not inherit it, seems to defeat the purpose. Regards, Barry kauler _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
