Hi everyone,
I have a quick question: is there a reason that we don't add `BuildArch: noarch` to source only go packages? To be clear, the `-devel` subpackages themselves have `BuildArch: noarch`, but the main packages don't. Unless I'm missing something, Koji still seems to create separate build jobs for each architecture.
Thanks, Maxwell
I think that the rational is basically this https://docs.fedoraproject.org/en-US/packaging-guidelines/#_use_noarch_only_... . In addition if I'm not mistaken koji will check that the noarch sub-packages are actually the same across all arches, else failing the build, but I'm not 100% sure about that. JC
Dec 20, 2021, 17:46 by gotmax@e.email:
Hi everyone,
I have a quick question: is there a reason that we don't add `BuildArch: noarch` to source only go packages? To be clear, the `-devel` subpackages themselves have `BuildArch: noarch`, but the main packages don't. Unless I'm missing something, Koji still seems to create separate build jobs for each architecture.
Thanks, Maxwell -- Maxwell G (@gotmax23) Pronouns: He/Him/His PGP Key Fingerprint: f57c76e5a238fe0a628e2ecef79e4e25e8c661f8 PGP Keyserver: hkp://keyserver.ubuntu.com gotmax@e.email
golang@lists.fedoraproject.org