On Donnerstag, 27. Februar 2025, 12:24:26 CET Dominique Leuenberger wrote:
On Thu, 2025-02-27 at 12:21 +0100, Adam Majer wrote:
On 2/27/25 11:05, Jiri Slaby wrote:
On a similar note: where is package meta for scmsync _projects_? Use case: Disable building some packages on some repositories. I.e. where to put: <build> <disable repository="15.6"/> <disable repository="Fedora_40"/> </build> ?
It will be part of the project meta BuildFlags.
https://src.opensuse.org/cockpit/_ObsPrj/src/branch/master/_config
BuildFlags: excludebuild:cockpit-suse-theme
%if "%_repository" == "openSUSE_Factory_ARM" || "%_repository" == "openSUSE_Tumbleweed"
BuildFlags: excludebuild:local-npm-registry %endif
Is way to disable builds now.
https://openbuildservice.org/help/manuals/obs-user-guide/cha-obs-prjconfig#s...
excluding builds and disabling builds is by far not the same (excludebuild wipes binaries for example, disable keeps them)
What about the rest of package meta, like useforbuild?
In general the goal is to obsolete the parallel meta information with the project git and having everything what we need in the sources. Either package sources or additional configuration files in the project. Build flags were often a problem since they could not be transfered into other projects as things like repository names did change. Also problems with old build results lead to issues where content is not rebuildable. So our vision so far is to obsolete them and try to stick to the exclude mechanic only. This can be specified in the package source already (eg. ExcludeArch in spec files or special tags in Dockerfile or kiwi files). We have no replacement for useforbuild yet. It could be added, but do we have really a usecase for it? In the past it caused mostly trouble. It is easy to add, if there is a usecase. -- Adrian Schroeter <adrian@suse.de> Build Infrastructure Project Manager SUSE Software Solutions Germany GmbH, Frankenstraße 146, 90461 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev