I think it's best to do as much as possible on the current versions before replacing them,īecause that process will be painful enough as it is. Like all of the above tooling/etc improvements, This is something that can be done before the new versions though, So I've decided to release zix and depend on it as a proper released and versioned library, This problem becomes more acute for several reasons, With the new versions I have in the pipeline, There is some sketchy code around that exists solely to work around this 'missing' dependency,Īnd still some questionable use of things to skirt around missing facilities (something like the role that glib plays in that ecosystem) has proven increasingly problematic. Meanwhile, the lack of a common lowest-level dependency for this kind of very boring and generic stuff Might technically be considered a violation of some distributions' policies (notably Debian's).

This has been troublesome from time to time when bugs need fixing,

(and some other developers have discovered this and taken bits for their own purposes as well).

In this case, I have three projects that use it: sord, lilv, and jalv More dependencies, more problems, but copy-paste code reuse certainly isn't without its own problems. I have some things that I just copy around piecemeal from project to project as necessary.Ī simple library of basic data structures and portability wrappers.īut I have never released it as a 'proper' library. It recently occurred to me, though, that there's one more incremental thing I can do here before 'ripping the band-aid off', so to speak. Has a consistent QC regime (high-coverage testing, multi-platform CI, strict compiler warnings, machine formatting, clean clang-tidy configurations, and so on),Īnd I'm finally starting to run out of changes that I can do without finally breaking the APIs and releasing new major versions.

So it will be easier to go back and do maintenance on the old versions where necessary.Īt this point, this process is almost done: everything uses meson now, This includes a lot of build system, tooling, and general quality control improvements. Mainly this is a task of trying to push as many changes back as I can,Īside from the usual bug fixes and code improvements, I've been working on new major versions of the LV2 host stack ( serd, sord, sratom, suil, and lilv) while maintaining the current stable versions.

Sfark to sf2 converter programs