Hi All, Fossil design clearly separates a project repository database from a checkout database. It is explicitly stated in the Fossil documentation:
http://fossil-scm.org/index.html/doc/trunk/www/tech_overview.wiki "Notice that the checkout database contains a pointer to the repository database but that the repository database has no record of the checkout databases. That means that a working checkout directory tree can be freely renamed or copied or deleted without consequence." Unfortunately, this in not true anymore since trunk [e604d483ee55] (2012-04-27 15:43:51). Now every time you "fossil open" a repository, the checkout root gets recorded into config portion of the project repo. All the checkouts ever created are displayed as "alt-root" entries by "fossil info". The "alt-root" list can get long if one has many checkouts. By the way, "fossil close" does *NOT* remove the entry from the alt-root list (a bug??). The list only grows and never shrinks. A convenient way of dispensing with checkouts by "rm -rf path-to-checkout" leaves behind dangling references to non-existing directories. To the best of my knowledge there has been no discussion of this feature on the fossil-users or fossil-dev mailing lists. Therefore, I would greatly appreciate if someone can explain to me (1) What is the purpose of the feature. (2) Its intended use. (3) Rational for violating long-standing Fossil design principle that project repo database does not know its checkouts. Thanks and Best Regards, --Leo-- _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
