devdocs:deploy_new_build_server
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
devdocs:deploy_new_build_server [2018/12/30 21:31] z5t1 |
devdocs:deploy_new_build_server [2019/01/04 21:25] z5t1 |
||
|---|---|---|---|
| Line 6: | Line 6: | ||
| - Edit the ''/opt/buildtools/config'' file and set the STAGING_SERVER variable to the appropriate value. | - Edit the ''/opt/buildtools/config'' file and set the STAGING_SERVER variable to the appropriate value. | ||
| - Edit the ''/etc/portsync.conf'' file and set the RSYNC_MIRROR variable to the staging server rsync mirror. | - Edit the ''/etc/portsync.conf'' file and set the RSYNC_MIRROR variable to the staging server rsync mirror. | ||
| + | - Edit the ''/etc/portmake.conf'' file and change the BUILD_PREFIX to the build prefix for the version of Cucumber Linux the build server is for. For example, if creating a build server for Cucumber Linux 2.0, which has been code named ''zaphod'', you would set ''BUILD_PREFIX=zaphod_''. | ||
| + | - Create the ports tree by running ''portstrap''. | ||
| + | - Set the timestamps on all of the files in ''/var/log/packages'' to the time you want to start building from. Any updates to the ports tree that took place after this time will trigger a rebuilding of the affected package. Any updates to the ports tree that took place before it will not. | ||
| + | - Alternatively, you can run ''pickle --update && pickle'' and install all the available updates. This will cause the build server to build any new updates, but skip any old ones. | ||
| + | - Run ''/opt/buildtools/auto_update'' to update the local files and build any updates. | ||
devdocs/deploy_new_build_server.txt ยท Last modified: 2019/01/07 17:12 by z5t1
Page Tools
