Fossil SCM
Clarified the issue of building and installing Git vs Fossil from source vs as binary packages in fossil-v-git.wiki
Commit
00af3dbf8bb20bc80667cf3f2f2aed5adf1f47c2d76c0e3cc435aa89a1660bbb
Parent
e88ae89c0fdff7c…
1 file changed
+7
-2
+7
-2
| --- www/fossil-v-git.wiki | ||
| +++ www/fossil-v-git.wiki | ||
| @@ -85,18 +85,23 @@ | ||
| 85 | 85 | |
| 86 | 86 | Git is actually a collection of many small tools, each doing one small |
| 87 | 87 | part of the job, which can be recombined (by experts) to perform |
| 88 | 88 | powerful operations. Git has a lot of complexity and many dependencies, |
| 89 | 89 | so that most people end up installing it via some kind of package |
| 90 | -manager, simply because these problems are best delegated to people | |
| 91 | -skilled in the creation of binary softare packages. | |
| 90 | +manager, simply because the creation of complicated binary packages is | |
| 91 | +best delegated to people skilled in their creation. Normal Git users are | |
| 92 | +not expected to build Git from source and install it themselves. | |
| 92 | 93 | |
| 93 | 94 | Fossil is a single self-contained stand-alone executable with hardly any |
| 94 | 95 | dependencies. Fossil can be run inside a minimally configured |
| 95 | 96 | [https://en.wikipedia.org/wiki/Chroot|chroot jail], from a Windows |
| 96 | 97 | memory stick, off a Raspberry Pi with a tiny SD card, etc. To install |
| 97 | 98 | Fossil, one merely puts the executable somewhere in the <tt>$PATH</tt>. |
| 99 | +Fossil is | |
| 100 | +[https://fossil-scm.org/fossil/doc/trunk/www/build.wiki|straightforward | |
| 101 | +to build and install], so that many Fossil users do in fact build and | |
| 102 | +install "trunk" versions to get new features between formal releases. | |
| 98 | 103 | |
| 99 | 104 | Some say that Git more closely adheres to the Unix philosophy, |
| 100 | 105 | summarized as "many small tools, loosely joined," but we have many |
| 101 | 106 | examples of other successful Unix software that violates that principle |
| 102 | 107 | to good effect, from Apache to Python to ZFS. We can infer from that |
| 103 | 108 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -85,18 +85,23 @@ | |
| 85 | |
| 86 | Git is actually a collection of many small tools, each doing one small |
| 87 | part of the job, which can be recombined (by experts) to perform |
| 88 | powerful operations. Git has a lot of complexity and many dependencies, |
| 89 | so that most people end up installing it via some kind of package |
| 90 | manager, simply because these problems are best delegated to people |
| 91 | skilled in the creation of binary softare packages. |
| 92 | |
| 93 | Fossil is a single self-contained stand-alone executable with hardly any |
| 94 | dependencies. Fossil can be run inside a minimally configured |
| 95 | [https://en.wikipedia.org/wiki/Chroot|chroot jail], from a Windows |
| 96 | memory stick, off a Raspberry Pi with a tiny SD card, etc. To install |
| 97 | Fossil, one merely puts the executable somewhere in the <tt>$PATH</tt>. |
| 98 | |
| 99 | Some say that Git more closely adheres to the Unix philosophy, |
| 100 | summarized as "many small tools, loosely joined," but we have many |
| 101 | examples of other successful Unix software that violates that principle |
| 102 | to good effect, from Apache to Python to ZFS. We can infer from that |
| 103 |
| --- www/fossil-v-git.wiki | |
| +++ www/fossil-v-git.wiki | |
| @@ -85,18 +85,23 @@ | |
| 85 | |
| 86 | Git is actually a collection of many small tools, each doing one small |
| 87 | part of the job, which can be recombined (by experts) to perform |
| 88 | powerful operations. Git has a lot of complexity and many dependencies, |
| 89 | so that most people end up installing it via some kind of package |
| 90 | manager, simply because the creation of complicated binary packages is |
| 91 | best delegated to people skilled in their creation. Normal Git users are |
| 92 | not expected to build Git from source and install it themselves. |
| 93 | |
| 94 | Fossil is a single self-contained stand-alone executable with hardly any |
| 95 | dependencies. Fossil can be run inside a minimally configured |
| 96 | [https://en.wikipedia.org/wiki/Chroot|chroot jail], from a Windows |
| 97 | memory stick, off a Raspberry Pi with a tiny SD card, etc. To install |
| 98 | Fossil, one merely puts the executable somewhere in the <tt>$PATH</tt>. |
| 99 | Fossil is |
| 100 | [https://fossil-scm.org/fossil/doc/trunk/www/build.wiki|straightforward |
| 101 | to build and install], so that many Fossil users do in fact build and |
| 102 | install "trunk" versions to get new features between formal releases. |
| 103 | |
| 104 | Some say that Git more closely adheres to the Unix philosophy, |
| 105 | summarized as "many small tools, loosely joined," but we have many |
| 106 | examples of other successful Unix software that violates that principle |
| 107 | to good effect, from Apache to Python to ZFS. We can infer from that |
| 108 |