[HELP] src/config.rs.ini vs src/config.rs about cargo-deb

[ximon18]

I'm not familiar with those gnome projects but looking at the source code of Amberol I see that it has some meson files.

I suspect that the project cannot be built using just a standard cargo invocation and instead requires that it be built using Meson. Cargo-deb has no way of knowing how to handle non-standard build systems.

What you could do is build it as it is supposed to built, then disable compilation via --no-build when invoking cargo-deb so that cargo-deb only packages already built artifacts.

[Baraccc]

It worked, not necessarily with amberol but with Fragments, whose instruction is in the project readme in gitlab.

Cargo-deb has no way of knowing how to handle non-standard build systems.

So no plan to support meson build system right?

[ximon18]

My brief, limited, impression of Meson is that it is intended to own the build process and so using --no-build with Cargo-deb is the right thing to do.

Though I have contributed to Cargo-deb in the past, I'm not the maintainer of Cargo-deb so I can only give you my opinion: the most likely way in my experience to extend Cargo-deb is to submit a pull request yourself with arguments explaining why it is a good proposal.