Why does OpenPKG focus on source RPMs only?
OpenPKG by design focuses on source RPMs and the building and installing directly from them. Binary RPMs are just an intermediate and temporary result in this approach. From our perspective, they exist just temporarily on the target machine or on our FTP server because of bootstrapping and for emergency situations only. There are multiple reasons for this. The most important are: • Stability: binary RPMs are inherently weak when it comes to run-time stability. The reason is that there are always differences between the build and install host — sometimes more, sometimes less. But just the smallest difference (versions of vendor shared libraries, different kernel patch-levels, system configuration differences, etc) can lead to a broken application on the install host due to inherited assumptions from the build host. Example: build host has higher configured maximum allowed size for shared memory segments (usually because runs also a RDBMS), building OSSP mm on it determines this high lim
*Sadly, we had to bring back ads too. Hopefully more targeted.