On Fri, Oct 15, 2021 at 12:39 AM Andrej Valek wrote:
>
> Ok, but I've just copied the existing commit from master. So I have to
> send a different configuration for dunfell?
Correct, for a stable release we don't want to change default
behavior. So we can't take the commit directly from master
Ok, but I've just copied the existing commit from master. So I have to
send a different configuration for dunfell?
Andrej
On Fri, 2021-10-15 at 10:58 +0100, Richard Purdie wrote:
> On Fri, 2021-10-15 at 06:15 +, Andrej Valek wrote:
> > The reason, why I want to apply it here, to switch
On Fri, 2021-10-15 at 06:15 +, Andrej Valek wrote:
> The reason, why I want to apply it here, to switch replace libidn2 with
> icu. According to libpsl documentation, you can chose who will generate
> the PSL database (libidn, libidn2, icu). So I don't want to install a
> new component if
The reason, why I want to apply it here, to switch replace libidn2 with
icu. According to libpsl documentation, you can chose who will generate
the PSL database (libidn, libidn2, icu). So I don't want to install a
new component if there is a valid replacement which is already
installed.
Regards,
On Wed, Oct 13, 2021 at 9:14 AM Valek, Andrej wrote:
> Would it be possible to include this commit
> https://lists.openembedded.org/g/openembedded-core/message/150627 into
> dunfell branch?
At first glance this seems to change the default behavior. Perhaps a
version of the patch that adds the
Hello Steve,
Would it be possible to include this commit
https://lists.openembedded.org/g/openembedded-core/message/150627 into
dunfell branch?
Thanks,
Andrej
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#156920):