Hi All, the recent changes to the trunk make "fossil open" to modify the fossil repository being opened. If this repository is read-only or mounted on a read-only file system than "fossil open" fails [2] and no _FOSSIL_ file is created.
I would prefer the solution proposed by Matt Welland [1] to keep all checkout information confined to ~/.fossil. A mere fact that someone called "fossil open" should not cause modifications to the project repository. "~/.fossil" is, on the other hand, a completely different story. Its purpose is precisely to help a user to organize its work with all his/her fossil repositories and their checkouts. --Leo-- [1] http://lists.fossil-scm.org:8080/pipermail/fossil-users/2012-April/009038.html [2] $ ~/Devel/Fossil/upstream/BUILD/fossil open ../T.fossil foo /home/leor/Devel/Fossil/upstream/BUILD/fossil: SQLITE_READONLY: statement aborts at 34: [REPLACE INTO config(name,value,mtime)VALUES('ckout:/tmp/fossil-tests/T/',1,now())] attempt to write a readonly database /home/leor/Devel/Fossil/upstream/BUILD/fossil: attempt to write a readonly database REPLACE INTO config(name,value,mtime)VALUES('ckout:/tmp/fossil-tests/T/',1,now()) If you have recently updated your fossil executable, you might need to run "fossil all rebuild" to bring the repository schemas up to date. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
