devdocs:build_system_infrastructure
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
devdocs:build_system_infrastructure [2018/11/15 21:11] z5t1 [Special Files] |
devdocs:build_system_infrastructure [2018/11/17 16:35] (current) z5t1 [Bootstrap Server] |
||
|---|---|---|---|
| Line 12: | Line 12: | ||
| - Build the initial Cucumber Linux from Scratch build. | - Build the initial Cucumber Linux from Scratch build. | ||
| + | - Create the initial ''CHANGELOG'', ''contents.bz2'', ''file-list'' and ''updates'' files. | ||
| + | - Upload the initial ports tree and package directories and ''CHANGELOG'', ''contents.bz2'', ''file-list'' and ''updates'' files to the staging server. | ||
| - Build the initial installation ISO images. | - Build the initial installation ISO images. | ||
| - | - Upload the initial ports tree and package directory to the staging server. | ||
| Line 58: | Line 59: | ||
| The CHANGELOG file used to be located at the root of the cucumber-x.y directory. It also used to track source changes as well as binary changes. In Cucumber Linux 2.0, this changed. The source code was migrated to Git, and Git commits became the primary method for tracking source code changes. This rendered the CHANGELOG file necessary only for tracking the binary changes. Since, with this change, the CHANGELOG became exclusively architecture specific, it made more sense to split it into separate files: one for each architecture. | The CHANGELOG file used to be located at the root of the cucumber-x.y directory. It also used to track source changes as well as binary changes. In Cucumber Linux 2.0, this changed. The source code was migrated to Git, and Git commits became the primary method for tracking source code changes. This rendered the CHANGELOG file necessary only for tracking the binary changes. Since, with this change, the CHANGELOG became exclusively architecture specific, it made more sense to split it into separate files: one for each architecture. | ||
| + | ==== cucumber-ARCH/contents.bz2 ==== | ||
| + | |||
| + | This file contains a list of all the files contained in each binary package for the entire distribution. Note that this is a lot of files, which results in the contents file being quite large, hence why it is bzipped. It is used by pickle when running ''pickle --file-search''. | ||
| + | |||
| + | ==== cucumber-ARCH/file-list ==== | ||
| + | |||
| + | This file contains a list of all the package files (*.txz files) located under the cucumber-ARCH directory. It is used by pickle for determining available packages. | ||
| + | |||
| + | ==== cucumber-ARCH/updates ==== | ||
| + | |||
| + | This file contains a list of updates to the binary packages. It is used by pickle when determining the available updates. | ||
devdocs/build_system_infrastructure.1542316261.txt.gz ยท Last modified: 2018/11/15 21:11 by z5t1
Page Tools
