Cristian Le

This PR is explicitly to unlock the packaging of `rust-config 0.15`. See https://src.fedoraproject.org/rpms/rust-config/pull-request/4

Thanks for the rebase, and sorry I didn't get back to it, it fell off my radar

I am packaging the dependency for rust-config. How about I ping you when it is ready to be merged (should be in 2 weeks)

Well, this fell off my radar entirely. There is a `rust-config0.13` compatibility package for all the remaining dependents so it is safe to merge this (was safe to do for...

If you wish to add something like `dependabot`, I can recommend using `renovatebot` instead. It does not polute the MRs and it can group across infrastructure, e.g. `pre-commit` + `github...

Hi, FetchContent is the recommended workflow for modern CMake because it allows the maximum flexibility for users, developers, packagers and downstream consumer. While it is designed for integrating with CMake...

Thanks for the explanation. Would it make sense to use a versioning like `4.6.0^YYYYMMDD`? On the Fedora packaging side unfortunately all sources must be vetted for licensing issues and uploaded...

> I am actually not sure how the config and TSL-s are licensed. This would depend on the distribution page, but I don't see anything obvious in the header metadata,...

Another point that will help is to understand the distinction between the various downloaded files: ```spec URL: https://github.com/open-eid/DigiDoc4-Client Source0: %{url}/releases/download/v%{version}/%{upstream_name}-%{version}.tar.gz # https://id.eesti.ee/config.json Source1: config.json # https://id.eesti.ee/config.pub Source2: config.pub # https://id.eesti.ee/config.rsa...

Sorry, I meant `config.qrc`