From: "Valek, Andrej" <andrej.valek@siemens.com>
To: "richard.purdie@linuxfoundation.org"
<richard.purdie@linuxfoundation.org>,
"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: [OE-core] libpsl: Add config knobs for runtime/builtin conversion choices
Date: Fri, 15 Oct 2021 10:39:48 +0000 [thread overview]
Message-ID: <4f983fee5101acf1a55c150a4a4ed1992b7199a4.camel@siemens.com> (raw)
In-Reply-To: <d1015886629914a9b2ca8dba71326ecf7b355bda.camel@linuxfoundation.org>
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 +0000, 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 there is a valid replacement which is already
> > installed.
>
> I think what Steve is suggesting is a tweaked version which doesn't
> change the
> current situation, just adds the PACKAGECONFIG options but doesn't
> change the
> current default.
>
> You could then change the configuration in your distro.
>
> Cheers,
>
> Richard
>
next prev parent reply other threads:[~2021-10-15 10:39 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
2021-10-15 9:58 ` [OE-core] " Richard Purdie
2021-10-15 10:39 ` Valek, Andrej [this message]
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=4f983fee5101acf1a55c150a4a4ed1992b7199a4.camel@siemens.com \
--to=andrej.valek@siemens.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=richard.purdie@linuxfoundation.org \
--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).