| 29 | | Since |
| | 29 | We have in the middle of chapter 5 an enter of the chroot environment. Typically, this is seen in the classic mechanism as the start of building the final system, therefore it was organized in a separate chapter, Chapter 6. |
| | 30 | |
| | 31 | In the new mechanism, this is no longer true. Entering the chroot environment the first time does not mean that now the build of the final system is startet. The activities in chroot env at this time are __still__ to prepare the toolchain. So, to make it more clear to the user, there are some options: |
| | 32 | |
| | 33 | 1) Introduce a new chapter |
| | 34 | * Chap 5: cross toolchain and cross built packages |
| | 35 | * Chap 6: temporary toolchain |
| | 36 | * Chap 7: final system |
| | 37 | * then for following chapters, add 1 |
| | 38 | |
| | 39 | 2) Keep classic organization |
| | 40 | * Chap 5: cross toolchain and cross built packages |
| | 41 | * Chap 6: final system |
| | 42 | * numbering of (following) chapters untouched |
| | 43 | |
| | 44 | but leaving the chroot env at end of chap5 and enter it again at the beginning of chap6. This seems quite redundant but it provides a logical cut between the two chapters as well as provides an exact entry point where building of the final system starts. That means, between leaving chroot after chapter 5 and reentering it at the beginning of chapter 6, this is the moment where the toolchain can be backed up. |
| | 45 | |
