Hello,
after collecting the requirements and a lot of discussions I published
now a document, which explains the requirements for a RPM, if it
should be used for transactional-update with RPMs,
transactional-update with OCI images build from this RPMs and
systemd-sysext images.
That article can be found at:
https://en.opensuse.org/openSUSE:Packaging_Requirements_for_Atomic_and_Imag…
Most of this is already defined by the FHS, our UsrEtc packaging
guidelines or other packaging guidelines, so it should not contain
anything surprising.
Next step will be to merge that with the old article about
transactional-update requirements and adjust the other packaging
guidelines.
Regards,
Thorsten
--
Thorsten Kukuk, Distinguished Engineer, Senior Architect, Future Technologies
SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461
Nuernberg, Germany
Managing Director: Ivo Totev, Andrew McDonald, Werner Knoblich (HRB
36809, AG Nürnberg)
Dear fellow openSuse packagers!
CMake prepares for a new major release 4.0. By default this will break every package that requires a minimum version of CMake <= 3.5.
Can we create in OBS a mass rebuild with the latest release candidate of CMake 4.0 to see the fallout? I don't know how to do it and if I am allowed to do so.
This would help to identify which package needs to be patched or even better, we can reach out to upstream with patches.
Is it worth to open an issue to track the packages which needs to be addressed?
By the way, SUSE libraries might be affected, too. For example libsolv has an according open merge request since last December, see
https://github.com/openSUSE/libsolv/pull/575
Bye
Christoph
--
Most customers will not accept source code with compile errors in it.
Dan Saks, CppCon 2016 (https://youtu.be/D7Sd8A6_fYU)
