On Tue, Jan 18, 2022 at 6:26 AM Ondrej Mosnacek <omosnace(a)redhat.com> wrote:
On Tue, Jan 18, 2022 at 12:19 PM Veronika Kabátová (via Email Bridge)
<cki-gitlab(a)redhat.com> wrote:
> From: Veronika Kabátová on
gitlab.com
>
https://gitlab.com/cki-project/kernel-ark/-/merge_requests/1538#note_8135...
>
> Yes, we can remove `glibc-static` from the RHEL env. ARK is *kinda* upstream
> so I'd need to double check we'd not break anything else by doing that,
since
> we inherited the binary from some upstream run in the past. I did offer this
> solution in the original email thread, and it is a possibility, but IMO it's
> not the whole solution in this case:
>
> One negative of doing that is that developers/users building the kernel on
> various local environments will run into the inconsistency of the configs that
> can puzzle them. Having either the config or the dependency stable (always
> on/off) would prevent the confusion. Basically what @prarit said about a known
> compile but across *any* environment.
Then how about adding `BuildConflicts: glibc-static` (+ an explaining
comment) to kernel.spec?
https://rpm-software-management.github.io/rpm/manual/spec.html#buildconfl...
Do "BuildConflicts" work with "dnf builddep"? Has anyone ever tried
that before? It'd be good to test to be sure it works. If it doesn't,
file a bug so it can be fixed.
--
真実はいつも一つ!/ Always, there's only one truth!