[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <23n92nss-8571-77p8-3026-7344145414o@vanv.qr>
Date: Fri, 14 Jul 2023 16:12:22 +0200 (CEST)
From: Jan Engelhardt <jengelh@...i.de>
To: Michal Suchánek <msuchanek@...e.de>
cc: linux-modules@...r.kernel.org, Takashi Iwai <tiwai@...e.com>,
Lucas De Marchi <lucas.de.marchi@...il.com>,
Michal Koutný <mkoutny@...e.com>,
Jiri Slaby <jslaby@...e.com>,
Masahiro Yamada <masahiroy@...nel.org>,
Nathan Chancellor <nathan@...nel.org>,
Nick Desaulniers <ndesaulniers@...gle.com>,
Nicolas Schier <nicolas@...sle.eu>,
linux-kbuild@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH kmod v2 3/4] kmod: Add config command to show compile
time configuration as JSON
On Friday 2023-07-14 16:02, Michal Suchánek wrote:
>>
>> What about doing it like systemd and generate a .pc file instead
>> that can then be queried like so, e.g.:
>>
>> $ pkg-config kmod --variable=modulesdir
>
> - .pc files would be shipped with libkmod development package, not the
> kmod tool in a binary distribution
On that point: No, they would not.
Again, confer with systemd: systemd.rpm(SUSE) provides systemd.pc,
systemd-devel.rpm provides libsystemd.pc. kmod.rpm would provide
kmod.pc, kmod-devel.rpm would continue to provide libkmod.pc as
it does today.
Powered by blists - more mailing lists