Fixed the documentation for update on pull --recurse-modules

Probably needs a -f
This commit is contained in:
reaction.la 2022-05-12 05:54:50 +10:00
parent ba1908f287
commit 7c04b7478f
No known key found for this signature in database
GPG Key ID: 99914792148C8388
6 changed files with 19 additions and 17 deletions

View File

@ -92,13 +92,12 @@
<p>Windows pre-requisites: Visual Studio and git-bash</p>
<p>To obtain the source code from which the project can be built, including
this README, from the bash command line (git-bash in windows).</p>
<pre class="bash2"><code>git clone missing url
cd wallet
./winConfigure.sh</code></pre>
<pre class="bash2"><code>git clone --recurse-submodules missing url</code></pre>
<p>To configure and build the required third party libraries in windows, then
build the program and run unit test for the first time, launch the Visual
Studio X64 native tools command prompt in the cloned directory, then:</p>
<pre class="bat"><code>winConfigure.bat</code></pre>
<p>Should the libraries change in a subsequent <code>pull --recurse-submodules</code> you will need to run <code>winConfigure.bat</code> again.</p>
<p>winConfigure.bat also configures the repository you just created to use
<code>.gitconfig</code> in the repository, causing git to to implement GPG signed
commits because <a href="./docs/contributor_code_of_conduct.html#code-will-be-cryptographically-signed" target="_blank" title="Contributor Code of Conduct">cryptographic software is under attack</a> from NSA
@ -127,7 +126,7 @@ For this to be useful you need to import the repository public key
<span id="cb3-12"><a href="#cb3-12" aria-hidden="true" tabindex="-1"></a><span class="co"># public gpg key repository. It should not be there.</span></span>
<span id="cb3-13"><a href="#cb3-13" aria-hidden="true" tabindex="-1"></a><span class="co"># Never use any email address on a gpg key related to this project</span></span>
<span id="cb3-14"><a href="#cb3-14" aria-hidden="true" tabindex="-1"></a><span class="co"># unless it is only used for project purposes, or a fake email,</span></span>
<span id="cb3-15"><a href="#cb3-15" aria-hidden="true" tabindex="-1"></a><span class="co"># or the email of someone whom you do not like.</span></span></code></pre></div>
<span id="cb3-15"><a href="#cb3-15" aria-hidden="true" tabindex="-1"></a><span class="co"># or the email of an enemy.</span></span></code></pre></div>
<p>To build the documentation in its intended html form from the markdown
files, execute the bash script file <code>docs/mkdocs.sh</code>, in an environment where
<code>pandoc</code> is available. On Windows, if Git Bash and Pandoc has been

View File

@ -14,9 +14,7 @@ To obtain the source code from which the project can be built, including
this README, from the bash command line (git-bash in windows).
```bash2
git clone missing url
cd wallet
./winConfigure.sh
git clone --recurse-submodules missing url
```
To configure and build the required third party libraries in windows, then
@ -27,6 +25,8 @@ Studio X64 native tools command prompt in the cloned directory, then:
winConfigure.bat
```
Should the libraries change in a subsequent `pull --recurse-submodules ` you will need to run `winConfigure.bat` again.
[cryptographic software is under attack]:./docs/contributor_code_of_conduct.html#code-will-be-cryptographically-signed
"Contributor Code of Conduct"
{target="_blank"}
@ -62,7 +62,7 @@ gpg --lsign 096EAE16FB8D62E75D243199BC4482E49673711C
# public gpg key repository. It should not be there.
# Never use any email address on a gpg key related to this project
# unless it is only used for project purposes, or a fake email,
# or the email of someone whom you do not like.
# or the email of an enemy.
```
To build the documentation in its intended html form from the markdown

View File

@ -4,8 +4,11 @@ title: Block chain structure on disk.
The question is: One enormous SQLite file, or actually store the chain as a collection of files?
In the minimum viable product, the blockchain will be quite small, and it will be workable to put it one big SQLite file.
The trouble with one enormous SQLite file is that when it gets big enough, we face a high and steadily increasing risk of one sector on the enormous disk going bad, corrupting the entire database. SQLite does not handle the loss of a single sector gracefully.
In the minimum viable product, the blockchain will be quite small, and it
will be workable to put it one big SQLite file. The trouble with one enormous
SQLite file is that when it gets big enough, we face a high and steadily
increasing risk of one sector on the enormous disk going bad, corrupting the
entire database. SQLite does not handle the loss of a single sector gracefully.
We will eventually need our own database structure designed around
Merkle-patricia trees, append only data structures, and accommodating a near

View File

@ -49,8 +49,9 @@ To install guest additions on Debian:
```bash
su -l root
apt-get -qy update && apt-get -qy install build-essential module-assistant git dialog rsync && m-a -qi prepare
apt-get -qy update && apt-get -qy install build-essential module-assistant git dialog rsync
apt-get -qy upgrade
m-a -qi prepare
mount -t iso9660 /dev/sr0 /media/cdrom
cd /media/cdrom0 && sh ./VBoxLinuxAdditions.run
usermod -a -G vboxsf cherry

View File

@ -107,14 +107,14 @@ namespace ro {
}
/*spaceship operator for any pair of types that
* do not already have a spaceship operator
* can be arguments for std::span
* and whose members have the spaceship operator
* noexistent values of the shorter array are considered zero if of
* arithmetic type, otherwise, considered greater than zero */
* nonexistent arithemetic values of the shorter array
* are considered zero
* Existent non arithmetic values are considered greater than
* nonexistent non arithemetic values */
template<class T, class U >
std::enable_if_t<!ro::has_spaceship_v<T,U>, decltype(std::span(declval<T>())[0] <=> std::span(declval<U>())[0]) >operator <=>(
const T& lh, const U& rh

View File

@ -1,10 +1,9 @@
#!/bin/bash
set -e
set -x
git config --local include.path ../.gitconfig
git submodule update --init --recursive
git submodule foreach --recursive 'git reset --hard'
git submodule foreach --recursive 'git clean -xdf'
git config --local include.path ../.gitconfig
set +e
set +x
rm -r x64