From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Andreas Müller" <schnitzeltony@gmail.com>,
"Ross Burton" <ross.burton@arm.com>
Cc: openembedded-core@lists.openembedded.org, nd@arm.com,
Steve Sakoman <steve@sakoman.com>,
cordlandwehr@kde.org
Subject: Re: [OE-core] [PATCH] libxml2: wrap xmllint to use the correct XML catalogues
Date: Sat, 03 Sep 2022 13:12:09 +0100 [thread overview]
Message-ID: <7e97fd1400dce9ce5bce3ba7273d0b35a326a171.camel@linuxfoundation.org> (raw)
In-Reply-To: <CALbNGRSb4WGO5Dwb-kz6Xeoc5My5a6n0q=n2hm+sid2ZuwrZmA@mail.gmail.com>
On Sat, 2022-09-03 at 12:11 +0200, Andreas Müller wrote:
> Hi,
>
> this is a major change on behaviour and causing trouble at least for
> KDE's kdoctools. Am no expert but I guess kdoctools uses custom
> catalogs. Worked around trouble in meta-qt5-extra (assume meta-kf5
> will face same) by preferring bare xmllint [1].
> Just a heads up - it is about to land in kirkstone - have no idea what
> this patch fixes.
>
> [1] https://github.com/schnitzeltony/meta-qt5-extra/blob/master/recipes-kde/kf5/tier2/kdoctools/files/0002-Prefer-bare-xmllint.patch
>
Thanks for the warning, I dropped it from the kirkstone pull request.
Does anyone know if that env var takes multiple paths?
If not, we probably need to adjust the wrapper to only set the envvar
if one isn't already set.
Cheers,
Richard
next prev parent reply other threads:[~2022-09-03 12:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-23 15:37 [PATCH] libxml2: wrap xmllint to use the correct XML catalogues Ross Burton
2022-09-03 10:11 ` [OE-core] " Andreas Müller
2022-09-03 12:12 ` Richard Purdie [this message]
2022-09-05 9:05 ` Ross Burton
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=7e97fd1400dce9ce5bce3ba7273d0b35a326a171.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=cordlandwehr@kde.org \
--cc=nd@arm.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@arm.com \
--cc=schnitzeltony@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