|
|
|
|
|
|
by ilyt
1303 days ago
|
|
|
Pretty much. I've built a few for the internal stuff and it is essentially one time effort for DEB based platform. Clowns at Red Hat do like to break manifest compatibility in the worst way tho, think "a macro with same name in new version now does something else". The idea of .spec file being whole manifest is... nice in theory, not in Red Hat execution. But then last time I did any for RHEL was at RH6/7 time, maybe it's better now... But even in that case that's fixing few minor things every 3-5 years at worst. There is no excuse to not make your packages if you're actual serious developer, not some random hobbyist. I do give a pass for apps that run as single binary as that while suboptimal is at least easy to work around. |
|
|
Being on Fedora I run into this a little more regularly than you would on proper RH these days, it's like the prerelease playground.
If you (or anyone) had things building fine for Fedora 36, they may not on 37. I forget which but one of the macros I repeat moved packages
One of these likely translates to a future Red Hat release