The minimum size I managed to get is 1.3 GB, that was with:
- Code: Select all
git clone --bare --depth=1 https://git.code.sf.net/p/flightgear/fgdata fgdata-bare-depth1
However, trying to work with the resulting repository ('git fetch --depth=3', etc.) quickly wanted to download
a lot of data, so finally I decided for a bare clone with full history:
- Code: Select all
git clone --bare https://git.code.sf.net/p/flightgear/fgdata fgdata.git-bare
This one takes 2.3 GB, not that bad considering that it will become 4.2 GB when made non-bare (bare = the normal files of the repo are not visible, but can be recreated from the Git internal data inside the repo).
So, the main file you need to get is
fgdata-bare-b45ae04c153.git.tar.gz. It is currently being uploaded, which should be finished in a few hours. There are signature files in the
same directory.
In the following, I assume that you've downloaded all files from that directory, and that it is now your current directory.
If you know how to use gpg[1], you can verify my OpenPGP signature on the *.SHA256SUM and *.SHA512SUM files, using the corresponding *.sign files:
- Code: Select all
% gpg2 --verify fgdata-bare-b45ae04c153.git.tar.gz.SHA256SUM.sign fgdata-bare-b45ae04c153.git.tar.gz.SHA256SUM
gpg: Signature made Thu 11 Jan 2018 11:23:04 PM CET
gpg: using RSA key 125B5A0FDB788FDD0EF41A9DC785B90B5053A3A2
gpg: Good signature from "Florent Rougon <...>" [ultimate]
gpg: aka "Florent Rougon <...>" [ultimate]
% gpg2 --verify fgdata-bare-b45ae04c153.git.tar.gz.SHA512SUM.sign fgdata-bare-b45ae04c153.git.tar.gz.SHA512SUM
gpg: Signature made Thu 11 Jan 2018 11:23:13 PM CET
gpg: using RSA key 125B5A0FDB788FDD0EF41A9DC785B90B5053A3A2
gpg: Good signature from "Florent Rougon <...>" [ultimate]
gpg: aka "Florent Rougon <...>" [ultimate]
%
Once you trust the *.SHA256SUM and *.SHA512SUM files, you can use them to check the integrity of your downloaded fgdata-bare-b45ae04c153.git.tar.gz:
- Code: Select all
% sha256sum -c fgdata-bare-b45ae04c153.git.tar.gz.SHA256SUM
fgdata-bare-b45ae04c153.git.tar.gz: OK
% sha512sum -c fgdata-bare-b45ae04c153.git.tar.gz.SHA512SUM
fgdata-bare-b45ae04c153.git.tar.gz: OK
%
Finally, let's unpack the tarball and set up this repository (i.e., make it non-bare and configure the 'origin' remote to fetch updates from the official FGData repo):
- Code: Select all
tar -xzf fgdata-bare-b45ae04c153.git.tar.gz
git clone fgdata.git-bare fgdata
cd fgdata
git remote set-url origin https://git.code.sf.net/p/flightgear/fgdata
git remote set-head origin next
You should now be able to update it with a simple 'git pull'. You can also remove the fgdata.git-bare directory in order to save space.
Good luck.
Edit: I simplified the instructions by removing output, and kept the default remote name 'origin' so as to avoid future confusion.
Edit 2: for better security in case the gpg verification step is not practicable (for you or anyone else), here are the contents of fgdata-bare-b45ae04c153.git.tar.gz.SHA256SUM:
- Code: Select all
1b88f6ea5840f0618c74718ae7894006ee598285f55845006c10763ec42ec02d fgdata-bare-b45ae04c153.git.tar.gz
and of fgdata-bare-b45ae04c153.git.tar.gz.SHA512SUM:
- Code: Select all
0ff5947527d3361df2d8a182a4c32128342cc418c36b594f7e06bd1653da2893c00c6370ee517c46caf184170f40502f77e59c57262c175dca1dc06301e5557f fgdata-bare-b45ae04c153.git.tar.gz
[1] This requires my OpenPGP key, instructions to get it can be found
here.