ping

> -----Original Message-----
> From: [email protected] <openembedded-
> [email protected]> On Behalf Of leimaohui
> Sent: Friday, August 21, 2020 12:00 PM
> To: [email protected]
> Subject: [OE-core] Why there is a RCONFLICTS in wireless-regdb recipe file
> 
> Hi,
> 
> There is a RCONFLICTS in wireless-regdb recipe file:
> -------------------------------------------
> # Install static regulatory DB in /lib/firmware for kernel to load.
> # This requires Linux kernel >= v4.15.
> # For kernel <= v4.14, inherit the kernel_wireless_regdb.bbclass # (in meta-
> networking) in kernel's recipe.
> PACKAGES = "${PN}-static ${PN}"
> RCONFLICTS_${PN} = "${PN}-static"    <---Here
> 
> FILES_${PN}-static = " \
>     ${nonarch_base_libdir}/firmware/regulatory.db \
>     ${nonarch_base_libdir}/firmware/regulatory.db.p7s \ "
> 
> -------------------------------------------
> 
> But I'm not understand why this parameter has been added? There is no
> conflict file between these two packages?
> Or for other reasons?
> 
> The following is the file list of wireless-regdb-static and wireless-regdb.
> -------------------------------------------
> /wireless-regdb/2020.04.29-r0/packages-split/wireless-regdb-static/
> └── lib
>     └── firmware
>         ├── regulatory.db
>         └── regulatory.db.p7s
> 
> 2 directories, 2 files
> -------------------------------------------
> wireless-regdb/2020.04.29-r0/packages-split/wireless-regdb
> ├── etc
> │   └── wireless-regdb
> │       └── pubkeys
> │           └── sforshee.key.pub.pem
> └── usr
>     └── lib
>         └── crda
>             └── regulatory.bin
> 
> 6 directories, 2 files
> -------------------------------------------
> 
> Best wished
> Lei
> 



-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#141799): 
https://lists.openembedded.org/g/openembedded-core/message/141799
Mute This Topic: https://lists.openembedded.org/mt/76323237/21656
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub  
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to