schroot: Even if `CONFIG_PACKAGE_schroot=m`, `SCHROOT_LVM=y` forces `CONFIG_PACKAGE_lvm2=y`, in 22.03.

Maintainer:

@jmarcet

Environment:

• OpenWrt git branch openwrt-22.03, latest git pull && ./scripts/feeds update -a && ./scripts/feeds install -a on 2022-08-25, ca. 08:00 UTC

Description:

When I select that schroot is built as a package but not installed to the final image by default, and I configure that schroot should support LVM2 snapshots:

CONFIG_PACKAGE_schroot=m
CONFIG_SCHROOT_LVM=y

the dependencies still force the lvm2-package together with it's library dependencies to be build into the image.

The dependencies are, as can be seen from make menuconfig:

Symbol: PACKAGE_lvm2 [=y]
Type  : tristate
[...]
Selected by [y]:
  - SCHROOT_LVM [=y]
Selected by [n]:
  - PACKAGE_schroot [=m] && y && SCHROOT_LVM [=y] && PACKAGE_lvm2-selinux [=m]<PACKAGE_schroot [=m]
  - PACKAGE_autopart [=m] && y && PACKAGE_lvm2-selinux [=m]<PACKAGE_autopart [=m]
  - PACKAGE_cryptsetup [=m] && y && PACKAGE_lvm2-selinux [=m]<PACKAGE_cryptsetup [=m]

I think this needs to be corrected to that lvm2 is only forced as an installable package but not forced to be baked into the image, when schroot is the same.

Regards!

Start with the schroot and LVM2 dependency definitions exposed by make menuconfig, using CONFIG_PACKAGE_schroot=m and CONFIG_SCHROOT_LVM=y as the reproduction. Trace why PACKAGE_lvm2 becomes y, then verify that the dependency remains available as a package without being forced into the final image.