Many hyperlinks are disabled.
Use anonymous login to enable hyperlinks.
|Comment:||Add the Why SQLite Does Not Use Git document.|
|Downloads:||Tarball | ZIP archive | SQL archive|
|Timelines:||family | ancestors | descendants | both | trunk|
|Files:||files | file ages | folders|
|User & Date:||drh 2018-04-10 00:21:14|
|01:09||Merge fixes from the 3.23.0 branch. (check-in: 2ca5d3c1c4 user: drh tags: trunk)|
|00:24||Add the Why SQLite Does Not Use Git document. (Cherrypick from trunk) (check-in: 50c596f536 user: drh tags: version-3.23)|
|00:21||Add the Why SQLite Does Not Use Git document. (check-in: 1b4a90faa0 user: drh tags: trunk)|
|12:02||Work on the "quirks.html" page. The page is still incomplete, but I need to divert attention to other issues so I'm checking in partial changes. (check-in: 508297d763 user: drh tags: trunk)|
> > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175
<title>Why SQLite Does Not Use Git?</title> <table_of_contents> <h1>Introduction</h1> <p> SQLite does not use the [https://git-scm.org|Git] version control system. SQLite uses [https://fossil-scm.org/|Fossil] instead. Fossil and Git are both block-chain version-control systems. They are both "distributed". They both store content has a sequence of immutable check-ins identified by a cryptographic hash. Git is wildly popular, to the point that many younger developers are familiar with nothing else. And yet, the developers of SQLite prefer Fossil. This article tries to explain why. <h1>A Few Reasons Why SQLite Does Not Use Git</h1> <ol> <li><p> With Git, it is very difficult to find the successors (decendents) of a check-in. <p> Git allows you to go backwards in time. Given the latest check-in on a branch, Git lets you see all the ancestors of that check-in. But Git makes it very difficult to move in the other direction. Given some historical check-in, it is quite challenging in Git to find out what came next. It can be done, but it is sufficiently difficult and slow that nobody ever does it. There is no button in GitHub that shows the descendents of a check-in. <p> This is a deal-breaker, a show-stopper. The principle maintainer of SQLite cannot function effectively without being able to view the successors of a check-in. This one issue is sufficient reason to not use Git, in the view of the designer of SQLite. <li><p> The mental model for Git is needlessly complex and consequently distracts attention from software under development. A user of Git needs to keep all of the following in mind: <ol type='a'> <li> The working directory <li> The "index" or staging area <li> The local head <li> The local copy of the remote head <li> The actual remote head </ol> <p> Git contains commands (or options on commands) for moving and comparing content between all of these locations. <p>In contrast, Fossil users only need to think about their working directory and the check-in they are working on. That is 60% less distraction. Every developer has a finite number of brain-cycles. Fossil requires fewer brain-cycles to operate, thus freeing up intellectual resources to focus on the software under development. <li><p> Git does not track branch history. This makes review of historical branches tedious. <p> As an example, consider display of a single historical branch of SQLite as rendered by GitHub and by Fossil: <ul> <li><b>GitHub:</b> [https://github.com/mackyle/sqlite/commits/prefer-coroutine-sort-subquery] <li><b>Fossil:</b> [https://sqlite.org/src/timeline?r=prefer-coroutine-sort-subquery] </ul> <p> The Fossil view clearly shows that the branch was eventually merged back into trunk. It shows where the branch started, and it shows two occasions where changes on trunk were merged into the branch. GitHub shows none of this. In fact, the GitHub display is mostly useless in trying to figure out what happened. <li><p> Git lacks native wiki and bug tracking. If you want these essential features, you have to install additional software such as GitLab, or else use a third-party service such as GitHub. And even then, the wiki and bug reports are centralized, not distributed. <li><p> Git requires more administrative support. Setting up a website for a project to use Git requires a lot more software, and a lot more work, than setting up a similar site with an integrated package like Fossil. <li><p>Nobody really understands Git. <img src="https://www.fossil-scm.org/fossil/doc/trunk/www/xkcd-git.gif"><br> (credit: [https://xkcd.com/1597/]) </ol> <h2>See Also</h2> <p>Other pages that talk about Fossil and Git include: <ul> <li><p>[https://fossil-scm.org/fossil/doc/trunk/www/fossil-v-git.wiki|Fossil vs. Git] <li><p>[https://www.fossil-scm.org/fossil/doc/trunk/www/quotes.wiki|What others say about Fossil and Git] </ul> <h1>A Git-User's Guide To Accessing SQLite Source Code</h1> <p> If you are a devoted Git user and have no intention of changing, you can still easily access SQLite. This section gives some hints on how to do so. <h2>GitHub Mirrors</h2> <p> There is a mirror of the SQLite source tree on GitHub at [https://github.com/mackyle/sqlite]. This mirror is maintained by user "mackyle" who is unaffiliated with, and unknown to, the official SQLite development team. We do not know mackyle, but we observe that he does a terrific job of keeping his mirror current, and so if you want to access the SQLite source code on GitHub, his mirror is the recommended source. <h2>Web Access</h2> <p> The [https://sqlite.org/src/timeline|SQLite Fossil Repository] contains links for downloading a Tarball, ZIP Archive, or [SQLite Archive] for any historical version of SQLite. The URLs for these downloads are simple and can be incorporated easily into automated tools. The format is: <center> <tt>https://sqlite.org/src/tarball/</tt><i>VERSION</i><tt>/sqlite.tar.gz</tt> </center> <p> Simply replace <i>VERSION</i> with some description of the version to be downloaded. The <i>VERSION</i> can be a prefix of the cryptographic hash name of a specific check-in, or the name of a branch (in which case the most recent version of the branch is fetched) or a tag for a specific check-in like "version-3.23.0". <h2>Fossil Access</h2> <p> Fossil is really easy to install and use. Here are the steps for unix. (Windows is similar.) <ol> <li> Download the self-contained Fossil executable from [https://fossil-scm.org/fossil/uv/download.html] and put the executable somewhere on your $PATH. <li><tt>mkdir ~/fossils</tt> <li><tt>fossil clone https://fossil-scm.org/fossil ~/fossils/sqlite.fossil</tt> <li><tt>mkdir ~/sqlite; cd ~/sqlite</tt> <li><tt>fossil open ~/sqlite.fossil .</tt> </ol> <p> Subsequently, to update your check-out, simply type: <blockquote> <tt>fossil up </tt><i>VERSION</i> </blockquote> <p> Use "trunk" for version to get the latest trunk version of SQLite. Or use a prefix of a cryptographic hash name, or the name of some branch or tag. <p> Use the "<tt>fossil ui</tt>" command from within the ~/sqlite checkout to bring up a local copy of the website.