[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230714135707.GI9196@kitsune.suse.cz>
Date: Fri, 14 Jul 2023 15:57:07 +0200
From: Michal Suchánek <msuchanek@...e.de>
To: Jan Engelhardt <jengelh@...i.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 v3] depmod: Handle installing modules under a prefix
Hello,
On Fri, Jul 14, 2023 at 03:38:18PM +0200, Jan Engelhardt wrote:
>
> On Friday 2023-07-14 14:21, Michal Suchanek wrote:
>
> >Some distributions aim at not shipping any files in / outside of usr.
> >
> >The path under which kernel modules are installed is hardcoded to /lib
> >which conflicts with this goal.
> >
> >+MODLIB = $(INSTALL_MOD_PATH)$(KERNEL_MODULE_PREFIX)/lib/modules/$(KERNELRELEASE)
>
> Ok, so if the problem statement is that hardcoded paths are bad, then why
> continue to hardcode the "/lib/modules" fragment? Just make it so that
> KERNEL_MODULE_PREFIX can be set to the exact string "/usr/lib/modules" and not
> just "/usr".
That's certainly an option.
The feature is modelled after the installation prefix option that can
move the whole filesystem hierarchy of installed files under /usr/local,
/opt, or any other directory of choice. However, in that case the
subdirectories in the hierarchy can be configured as well while in this
case /lib/modules remains hardcoded.
Making it possible to set the whole path is generally more flexible
although there is no need to set the later part for this particular use
case.
Thanks
Michal
Powered by blists - more mailing lists