Hello Packagers, Long story short: A not insignificant part of the rust2rpm code base is dedicated to dealing with non-crate packages (i.e. running rust2rpm with "--path <path>" for a local Cargo.toml file, instead of pointing it at a crate from crates.io).
This mode of operation requires special-cased code paths, additional jinja2 templates, and in some cases, quite complicated logic - all just to render RPM spec files that aren't even "complete" (or usable) as-is - in contrast to the automagic and ready-to-use spec file creation for Rust crates from crates.io. In most cases, the *only* differences between a spec file rendered by rust2rpm and a copy-pasted template from documentation would be that the "Name" and "Version" tags in the spec file (and the most obvious %files entries) would already be filled in ... and, in some edge cases, not even correctly. That is a ridiculously small amount of "functionality" on top of "copy-paste this template" in relation to the amount of code that is required to make it work. So, I'm proposing to remove the support code (and templates, etc.) for this mode of operation from rust2rpm with the next major version, and to replace it with documentation - including one or two spec file templates for the use cases that are then no longer covered by rust2rpm. What do you think? Fabio -- _______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
