diff options
| author | Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> | 2020-08-11 15:37:26 +0200 |
|---|---|---|
| committer | Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org> | 2020-08-11 15:37:48 +0200 |
| commit | f80f0f1aec388d7bb70e2133e4ceedb1133c07cd (patch) | |
| tree | 23bc0d668a903fb68433b0080709a54a33e36bf0 | |
| parent | a61a00ca539a9631a8138b5bede7a860fe64cfa3 (diff) | |
| download | vendor_replicant-release-scripts-f80f0f1aec388d7bb70e2133e4ceedb1133c07cd.tar.gz vendor_replicant-release-scripts-f80f0f1aec388d7bb70e2133e4ceedb1133c07cd.tar.bz2 vendor_replicant-release-scripts-f80f0f1aec388d7bb70e2133e4ceedb1133c07cd.zip | |
Release procedure: mention approximate size requirements
Signed-off-by: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
| -rw-r--r-- | README.txt | 23 |
1 files changed, 16 insertions, 7 deletions
@@ -68,13 +68,22 @@ tag. Doing it from scratch will make sure that the repositories are fetchable and that nothing went wrong. -Once this is done, you can finally start building all the images with -releasebuild.sh. The build process can many hours on an older computer, so it's -a good idea to plan that ahead. For instance, if your build computer is noisy -and that its noise can prevent you from sleeping, you might want considering -launching the build as soon as you wake up the morning to have it finished -before you need to go to sleep, or if it's possible you might also want to -consider moving that computer before starting the build. +Once this is done, it would be a good idea to make sure that you have enough +space for building the release: For a release, you will need to build Replicant +for all the supported devices, so it can take more space than usual. + +As a point of comparison, for the Replicant 6.0 0004 RC2 release which supported +10 targets (espresso3g, espressowifi, i9100, i9300, i9305, maguro, n5100, n5110, +n7000, n7100) after the build the replicant-6.0 directory took about 219 GiB +(228773716 bytes). + +After that, you can finally start building all the images with releasebuild.sh. +The build process can many hours on an older computer, so it's a good idea to +plan that ahead. For instance, if your build computer is noisy and that its +noise can prevent you from sleeping, you might want considering launching the +build as soon as you wake up the morning to have it finished before you need to +go to sleep, or if it's possible you might also want to consider moving that +computer before starting the build. At the time of writing, around the end of the build of the first target, it will ask you some information for a certificate, so make sure to be around |