On 11 September 2014 13:50, Andy Bradford <amb-sendok-1413049836.aenikllhaaeaihnhp...@bradfords.org> wrote: > Actually, it does work. The problem isn't with the versionable setting. > There is a bug, but its in fossil open, not the setting. > > After you open the fossil, delete the link (which is actually now a > file) and then do fossil update. It should come back as a link.
Quite right! Unfortunately, this makes it kind of difficult. And the kind of thing you'd never remember when it finally bites you. I'm sure the fix is fairly straightforward, but I can't look at it today. Fortunately, in the short term just using the setting is fine. There's also the minor bug that "fossil unset allow-symlinks" gives you a warning and tells you to run exactly that command! Thanks for your help... now on to figure out how to clone over ssh. ../Dave ----------- script follows ------ #! /bin/sh FOSSIL=~/Fossils/foo.fossil rm -rf foo* *~ .fossil* .fslckout $FOSSIL set -x fossil version mkdir foo-dir touch foo-dir/foo-file ln -s foo-dir foo-link mkdir .fossil-settings echo yes >.fossil-settings/allow-symlinks ls -ld * .fossil*/* cat .fossil-settings/allow-symlinks rm -f $FOSSIL fossil new $FOSSIL fossil open $FOSSIL fossil settings allow-symlinks yes fossil add .fossil-settings fossil ci -m settings #fossil settings allow-symlinks no fossil unset allow-symlinks fossil add * fossil ci -m test rm -rf ../foo-alt mkdir ../foo-alt cd ../foo-alt fossil open $FOSSIL ls -l rm foo-link fossil update ls -l _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
