Thank you all for your answers

BR

Den fre 4 feb. 2022 kl 16:29 skrev Mikko Rapeli <[email protected]>:
>
> Hi,
>
> On Fri, Feb 04, 2022 at 04:03:52PM +0100, Joakim Roubert wrote:
> > On 2022-02-04 15:30, Mans Zigher wrote:
> > >
> > > with our current understanding our customer cannot comply with GPLv3
> > > so we have to avoid it at all cost.
> >
> > I think this is a situation where
> >
> > https://layers.openembedded.org/layerindex/branch/master/layer/meta-gplv2/
> >
> > might come in handy, together with something like
> >
> > PREFERRED_VERSION_bash ?= "3.2.%"
> >
> > in the local.conf (or similar suitable configuration place).
>
> While this would work, I can't recommend using meta-gplv2 as it contains 
> unmaintained
> SW versions.
>
> Just configure the build to avoid GPLv3 via distro config, e.g.
>
> INCOMPATIBLE_LICENSE_append += " GPLv3 GPLv3+ LGPLv3 LGPLv3+"
>
> and configure SW components to build without GPLv3 dependencies.
> lxc for examples compiles just fine without rsync and bash.
>
> Additionally a lot of GPLv3 recipes can be enabled to build but be forbidden
> images images, e.g. in distro config:
>
> WHITELIST_GPL-3.0 += "bash"
> PACKAGE_EXCLUDE += "bash-ptest bash-dbg bash-staticdev bash-dev bash-doc 
> bash-locale bashbug bash"
>
> Some refactoring of SW architecture may be needed to remove any dependencies 
> to GPLv3
> licensed SW. For development and testing GPLv3 components can often be used.
>
> Cheers,
>
> -Mikko
> 
>
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#7053): 
https://lists.yoctoproject.org/g/meta-virtualization/message/7053
Mute This Topic: https://lists.yoctoproject.org/mt/88903092/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-virtualization/unsub 
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to