Resolve conflict with /lib/modules when using baselibs
authorHyotaek Shim <hyotaek.shim@samsung.com>
Wed, 23 Jun 2021 01:15:47 +0000 (10:15 +0900)
committerHyotaek Shim <hyotaek.shim@samsung.com>
Wed, 23 Jun 2021 01:32:46 +0000 (10:32 +0900)
commit420a22a4c1179c0c2e5225a98a85204603848a45
tree60b05afccc08b51bfaf877e906b1535391dce652
parent290ab22c8effa3c42d7971a0ad028dc5749cf8c8
Resolve conflict with /lib/modules when using baselibs

In tw3 images, kernel is based on 64bit while platform is on 32bit.
Thanks to baselibs, aarch64 rpms containing tw3 kernel modules can be repackaged to arm rpms.

$ rpm -ql linux-tizen-modules-tw3-aarch64-6.5.0-0.armv7l.rpm
/lib/modules
/lib/modules/4.9.59
/lib/modules/4.9.59/extra
/lib/modules/4.9.59/extra/logger.ko

Unfortunately, however, /lib/modules, which is implicitly packaged,
is conflict with filesystem package.

INFO: Next install: filesystem
WARNING: file /lib/modules conflicts between attempted installs of
linux-tizen-modules-tw3-aarch64-6.5.0-1.1.armv7l and filesystem-3.1-3.3.armv7l
ERROR: Could not run transaction.

This patch avoids generating /lib/modules in the linux-tizen-modules-tw3-aarch64.armv7l.rpm

Change-Id: I8be870f9999e1e2f626c99bae7bced3ac623d44d
Signed-off-by: Hyotaek Shim <hyotaek.shim@samsung.com>
packaging/baselibs.conf
packaging/linux-tizen-modules.spec