I'm still a beginner at using Fossil (or any version control management system) but I have managed to get my 'Woof' project into a Fossil repository.
However, in the process I have identified four limitations of Fossil that are a problem for hosting Woof. I have added to my Fossil Quick Guide page explaining these limitations (scroll down near bottom): http://bkhome.org/fossil/fossil-guide.htm I have written a wrapper script named 'fossil', and renamed the binary executable to 'fossil.bin'. If you want to see the 'fossil' script, grab the fossil PET package from here: http://distro.ibiblio.org/pub/linux/distributions/puppylinux/pet_packages-4/fossil-20091111.pet Note that a PET package is just a gzipped tarball with a md5sum appended to the file. So, doing this will expand it (tar will complain about stuff on the end of the file): > tar -zxf fossil-20091111.pet ...it will expand into directory 'fossil-20091111' (PET binary packages do not expand directly into /). There may be problems with my script, only limited testing so far, and I've only made limited use of the fossil commandline options. If there's anything dumb in how I've done these workarounds, let me know. Regards, Barry Kauler _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
