February 9, 2023

SHSU Houstonian Online

Read all latest news headlines from USA, UK and around the world, get today's breaking news and live updates on politics, elections, business, sports, economy,​ …

Rocky Linux 9 has appeared with a new build system – Computer – News

why does it matter?

No company has little sense or vision that they will use any distro without first checking whether there is sufficient (paid) support for it and whether the necessary software they want to use can also run.

These kind of distros are nice niche products for the hobby club and a few enthusiasts who can do everything themselves and know it better. In the end, it is simply doomed to failure because without commercial support distribution would not be more than a pleasure for the hobby and small and medium businesses. Every slightly larger company uses commercially supported distributions simply because they cannot put the company in the hands of an amateur club.

Another build system means absolutely nothing, as long as the compiler and compiler settings are the same, the only real difference is the way the code and artifacts are placed in the right place and how the formatting works around them. Consider choosing a CI/CD tool… Jenkins pipeline or Shipable pipeline doesn’t really make a difference, everything in the shell or at least the Python scripts doesn’t make a difference, the end result is 100% the same.
Of course working with one will be easier than the other and you can have an endless discussion about the right choice. I can tell you from experience that it doesn’t really matter and the most important thing is that the system does what you need and is flexible enough to present you with possibilities in the future (as much as you can estimate of course). Make the buildings the way you want them.

See also  trash (not aliens)

I can create 100 identical builds with 10 different build systems in 10 different ways, which are 100% compatible with binary. The only important thing is that the build system generates the correct output, eg. Slack message When a certain point in the build is reached, the test results are sent to another system. The ability to have the build automatically put artifacts into another repo if they meet certain criteria (successful tests, for example). I may want to use the last successful build of that dependency if the build of the dependency fails (may be useful if you want to test new SSH tools for example and don’t care at all about this potential new version of netcat which is also in this expected build)

There are countless reasons to switch building systems or choose Building System A over Building System B. All of which are very good reasons, but in the end the most important thing is the result and in this particular case the result is 100% equal to building RetHat Enterprise Linux. All the other bells and whistles don’t matter if you can’t promise 100% compatibility, and it’s often a lot easier than it might seem if you switch build systems.