rpm2module might be misleading. Rename it so the user knows what to expect. We could use package2modulemd or some shorter form of it (pkg2modulemd, pkg2mmd...)
I am personally -1 on this. rpm word in these kind of modules is well-established standard:
rpm
pyp2rpm.noarch : Convert Python packages to RPM SPECFILES rubygem-gem2rpm.noarch : Generate rpm specfiles from gems python3-rust2rpm.noarch : Convert Rust packages to RPM
@ttomecek and what do you think about the module->modulemd part?
module is shorter :)
module
Honestly, I don't have opinion there. module is probably better because usually these tools refer to final artifacts, not build recipes.
I'm going to close this one, as naming the tool after the binary artifact is common, even though the tool actually produces a spec for the binary artifact (e.g. all the x2rpm tools produce an RPM spec file, not an RPM directly).
Metadata Update from @ncoghlan: - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.