Hi, On Fri, Feb 18, 2022 at 09:03:53AM +0100, Alexander Kanavin wrote: > You should really try per-image INCOMPATIBLE_LICENSE :) Maintaining > those whitelists/excludes is awkward, as developers constantly want > more of them.
Hmm, this rings a bell. Likely yes then :) But on the other hand this way we're quite explicit about what GPLv3 things we allow to compile. Compiling too much also hurts with compilation times too and for many use cases developers are better off working with Debian or Ubuntu tooling than compiling every bell and whistle with yocto. My list of GPLv3 recipes enabled for compilation is quite stable at: autoconf bash bc binutils bison cairo ccache coreutils diffutils elfutils findutils gawk gcc gdb gdbm gettext gnutls grep libevent libmpc libpipeline libunistring m4 make mpfr python-rfc3987 python-strict-rfc3339 readline rsync sed tcpreplay which Cheers, -Mikko
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#161886): https://lists.openembedded.org/g/openembedded-core/message/161886 Mute This Topic: https://lists.openembedded.org/mt/89228507/21656 Group Owner: openembedded-core+ow...@lists.openembedded.org Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
