On Dienstag, 25. März 2025 14:34:58 Mitteleuropäische Normalzeit Dan Čermák wrote:
Hi Thomas,
...
Or are there some internally documented flags?
I am only aware of https://en.opensuse.org/openSUSE:Build_Service_cross_distribution_howto
Thanks!
This makes a lot of sense to reduce complexity. But if I see this correctly, it's not possible to reduce package dependencies only for Enterprise projects?
You can make dependencies also conditional on packages that only exist in Leap and those that only exist in SLE, e.g.: --8<---------------cut here---------------start------------->8--- Requires: (SLE_dependency if (product(SL-Micro) or (product(SUSE_SLE)
= 15.5))) Suggests: (Leap_dependency if openSUSE-release) --8<---------------cut here---------------end--------------->8---
Not sure I get this, above is not the correct syntax? That would mean the BuildRequires are fix for all build flavors or in other words: Because there is only one build flavor. But the Requires: could be differed. But this would only work for "soft" Requires where some kind of conditional/ dynamic loading of libraries/plugins at runtime is supported? In my case C libraries seem to be a hard requirement defined at build time. Depending on whether I build against libimobiledevice/libplist, the build system auto-adds the Requires: rpm -qpR upower-1.90.7.13+git.4f1ef04-0.x86_64.rpm ... libimobiledevice-1.0.so.6()(64bit) libplist-2.0.so.4()(64bit) ... Thanks a lot for the details, even it seem not to help in my case. I guess I go for all package dependencies, possibly provide a not used rpm define in case someone wants to remove the dependencies manually. Thanks, Thomas