|
From: Scott C. <sc...@cu...> - 2018-07-12 18:30:30
|
Hello All, I am pleased to announce the immediate availability of Cucumber Linux sysbuild 18001. What is a sysbuild you may ask? Every time Cucumber Linux is rebuilt from scratch, it has the potential to end up with a new ABI. Recently, I wrote an article about how to build Cucumber Linux from scratch (https://z5t1.com/cucumber/wiki/cucumber_linux_from_scratch). Now that we have transitioned approximately one third of the packages in the binary distribution to the new build system format, it has become much easier to rebuild the system from scratch. This is good because it makes it much easier to test ABI breaking changes. The drawback to this though is that it will result in a large amount of ABI diversity across different development builds. In order to differentiate between the different ABIs, each new build of the system will be given a unique sysbuild number to identify it. More details and a list of sysbuilds can be found at https://z5t1.com/cucumber/wiki/devdocs:sysbuild_numbers. This new sysbuild was built from the Cucumber Linux 2.0 source tree. I have tagged the point at which it was built as a pre-release (https://github.com/cucumberlinux/ports/releases/tag/sysbuild18001). This build contains only the packages found in phase 2 and will receive no security updates. It is intended to be used only in testing environments, primarily for testing the new toolchain and system utilities. *Do not use it in a production environment*. Once enough of the phase 3 packages are updated for the ports tree to become self hosted I will make a second sysbuild. That sysbuild will become the first alpha for Cucumber Linux 2.0 and will be used to build the rest of the packages in the ports tree once they get updated. You can download sysbuild 18001 at https://cucumberlinux.com/all_downloads.php#sysbuild18001. Happy Hacking, - Scott |
