From: "Valek, Andrej" <andrej.valek@siemens.com>
To: "steve@sakoman.com" <steve@sakoman.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"raj.khem@gmail.com" <raj.khem@gmail.com>
Subject: Re: libpsl: Add config knobs for runtime/builtin conversion choices
Date: Fri, 15 Oct 2021 06:15:40 +0000 [thread overview]
Message-ID: <56ce3d16404402d0b6661fb067c587618a57661f.camel@siemens.com> (raw)
In-Reply-To: <CAOSpxdaGuK2RqNGz2VJg04AhnDhVRAMYvOLS497d-OTYUoXc-Q@mail.gmail.com>
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,
Andrej
On Thu, 2021-10-14 at 07:36 -1000, Steve Sakoman wrote:
> On Wed, Oct 13, 2021 at 9:14 AM Valek, Andrej
> <andrej.valek@siemens.com> wrote:
>
> > Would it be possible to include this commit
> > https://lists.openembedded.org/g/openembedded-core/message/150627 i
> > nto
> > dunfell branch?
>
> At first glance this seems to change the default behavior. Perhaps a
> version of the patch that adds the knobs but keeps the same behavior?
>
> I may be mistaken since I'm not really familiar with this package, so
> would love input from those who are!
>
> Steve
next prev parent reply other threads:[~2021-10-15 6:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 19:13 libpsl: Add config knobs for runtime/builtin conversion choices Valek, Andrej
2021-10-14 17:36 ` Steve Sakoman
2021-10-15 6:15 ` Valek, Andrej [this message]
2021-10-15 9:58 ` [OE-core] " Richard Purdie
2021-10-15 10:39 ` Valek, Andrej
2021-10-15 15:45 ` Steve Sakoman
2021-10-16 18:40 ` [OE-core][dunfell][PATCH] " Andrej Valek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56ce3d16404402d0b6661fb067c587618a57661f.camel@siemens.com \
--to=andrej.valek@siemens.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=steve@sakoman.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).