Patrick

So I think a feature that: - Adds a `cargo` buildsystem that runs the normal `cargo` commands to build/test/install - Add a `cargo-lock` source type that expands into regular sources,...

> I'm not sure what the sentence "Extension define extension points in the app/runtime that can be implemented by extensions, supplying extra files which are available during runtime" is really...

The entry point is https://github.com/flatpak/flatpak-builder/blob/main/tests/test-builder.sh They are just simple shell scripts.

So we need to make this have value beyond what `buidlsystem: simple` just calling `cargo` does. That means that we have something that actually expands Cargo sources or similar.

I have no opinion at all of TOML libraries. On Fedora these are packaged: - ~~[libtoml](https://github.com/ajwans/libtoml) (C) (DEAD)~~ - [toml11](https://github.com/ToruNiina/toml11) (C++ Header) - [tomlplusplus](https://github.com/marzer/tomlplusplus) (C++) - ~~[cpptoml](https://github.com/skystrife/cpptoml) (C++) (DEAD)~~

Not packaged but maybe interesting: - [tomlc99](https://github.com/cktan/tomlc99) (C) - ~~[tomlc](https://github.com/mzgoddard/tomlc) (C) (DEAD)~~

I think I'd lean towards tomlc99 as a Meson subproject.

> and autotools has a --disable-Werror option (if using AX_COMPILER_FLAGS) Well `flatpak-builder` can't know if thats used or not and would just be passing potentially problem causing arguments (if it...

Well a benefit of the checksum being in the manifest is you actually know when things change. If its a remote resource they can both change.

Did this work in 1.2.x?