Hello, Am Donnerstag, 17. Dezember 2020, 14:59:36 CET schrieb Fabian Vogt:
Previously, packages with multiple spec files (e.g. systemd, which has both systemd.spec and systemd-mini.spec) needed a .changes file for each .spec. As the vast majority of changes (e.g. version updates) affect all "flavors", this requirement got dropped and only a single .changes file with the name used for the submit request is needed. It's used for all .spec files during build.
What's the recommended way for existing packages with multiple spec files? Merge the changes files into one, or keep separate changes files for each spec? I'm especially asking about the apparmor (and libapparmor) package: https://build.opensuse.org/package/show/security:apparmor/apparmor libapparmor was split into its own spec to fix a build dependency loop, and libapparmor.changes contains only libapparmor-related changes - but most of that information is also in apparmor.changes. What's your recommendation in this case? Bonus question: will the package still build for Leap 15.x with only one changes file? Regards, Christian Boltz -- Natürlich kann ich Traktor fahren. Ich bin der geborene Traktorfahrer. Es dürfte dir schwer fallen, jemanden zu finden, der annähernd so perfekt Traktor fährt wie ich. Ja, ich _bin_ geradezu ein Traktor. Wieviele Räder hat so ein Traktor eigentlich? [Ratti]