Fossil SCM
Added more reasons not to use Fossil as a whole-system configuration backup utility in the glossary point about not using Fossil to store files scattered hither-and-yon over a filesystem.
Commit
7994809763365ac6acb2c08f39c1b119cd69ac9fa88587b296e5657e2bc0a5c2
Parent
78aa43940719f3c…
1 file changed
+6
+6
| --- www/glossary.md | ||
| +++ www/glossary.md | ||
| @@ -83,10 +83,16 @@ | ||
| 83 | 83 | try to use Fossil as a system deployment tool by archiving versions |
| 84 | 84 | of the OS configuration files and then unpacking them on a new |
| 85 | 85 | system, the extracted project files would have read/write access by |
| 86 | 86 | the user who did the extraction, which probably isn’t want you were |
| 87 | 87 | wanting. |
| 88 | + | |
| 89 | + Even with these problems aside, do you really want a `.fslckout` | |
| 90 | + SQLite database at the root of your filesystem? Are you prepared for | |
| 91 | + the consequences of saying `fossil clean --verily` on such a system? | |
| 92 | + We believe Fossil is a poor choice for a whole-system configuration | |
| 93 | + backup utility. | |
| 88 | 94 | |
| 89 | 95 | And as a counter-counterexample, a project made of your user’s [Vim] |
| 90 | 96 | configuration is a much better use of Fossil, because it’s all held |
| 91 | 97 | within `~/.vim`, and your user has full rights to that subdirectory. |
| 92 | 98 | |
| 93 | 99 |
| --- www/glossary.md | |
| +++ www/glossary.md | |
| @@ -83,10 +83,16 @@ | |
| 83 | try to use Fossil as a system deployment tool by archiving versions |
| 84 | of the OS configuration files and then unpacking them on a new |
| 85 | system, the extracted project files would have read/write access by |
| 86 | the user who did the extraction, which probably isn’t want you were |
| 87 | wanting. |
| 88 | |
| 89 | And as a counter-counterexample, a project made of your user’s [Vim] |
| 90 | configuration is a much better use of Fossil, because it’s all held |
| 91 | within `~/.vim`, and your user has full rights to that subdirectory. |
| 92 | |
| 93 |
| --- www/glossary.md | |
| +++ www/glossary.md | |
| @@ -83,10 +83,16 @@ | |
| 83 | try to use Fossil as a system deployment tool by archiving versions |
| 84 | of the OS configuration files and then unpacking them on a new |
| 85 | system, the extracted project files would have read/write access by |
| 86 | the user who did the extraction, which probably isn’t want you were |
| 87 | wanting. |
| 88 | |
| 89 | Even with these problems aside, do you really want a `.fslckout` |
| 90 | SQLite database at the root of your filesystem? Are you prepared for |
| 91 | the consequences of saying `fossil clean --verily` on such a system? |
| 92 | We believe Fossil is a poor choice for a whole-system configuration |
| 93 | backup utility. |
| 94 | |
| 95 | And as a counter-counterexample, a project made of your user’s [Vim] |
| 96 | configuration is a much better use of Fossil, because it’s all held |
| 97 | within `~/.vim`, and your user has full rights to that subdirectory. |
| 98 | |
| 99 |