On Mon, Sep 29, 2025 at 05:35:01PM +0200, Oleksii Kurochko wrote:
>
> On 9/29/25 2:07 PM, Anthony PERARD wrote:
> > The library YAJL has been unmaintained for several years, without an obvious
> > fork to pick.
> >
> > On the other and the library json-c is been maintained and use by several other
> > project, it's probably already installed on your machine. So this patch series
> > intend to allow to build the Xen toolstack again json-c, and forgo yajl.
>
> Do we have any plans to drop fallback to yajl in the next release? Or because of
> this ...
Do we need a plan? We still have to support ancient version of several
dependencies, and json-c is a fairly recent project. In any case, usage
of yajl is quite contained, so I don't think it's a problem to let it
rot, and remove it when it get broken for long enough, but that's
unlikely to happen.
> >
> > Just in case, YAJL is can still be used.
> >
> > There's bit of libxl API that exposes YAJL, mainly so it can be used by `xl` to
> > call libxl_domain_config_gen_json(). It was exposed via the "libxl_json.h"
> > headers. This functions and others won't be available when libxl is build
> > against json-c.
>
> ... that some API trying to use API exposed by YAJL we just can't drop support
> of yajl?
Well, I'm hopping those API are only used by `xl` and nothing else. And
to be fair, I've seen few project dropping support for YAJL and use
json-c instead (libvirt, to name one), so they can't use those API.
Cheers,
--
Anthony PERARD