On 17. 11. 23 22:37, Fabio Valentini wrote:
Hi all, I'm sorry in advance for the wall of text below, but I think it adds some necessary context to this issue. The cargo RFC for "Packages as (optional) namespaces" was recently approved, and will likely be implemented in a future version of cargo, and on the official package registry, crates.io: c.f. https://github.com/rust-lang/cargo/issues/12901 c.f. https://github.com/rust-lang/rfcs/pull/3243
[...]
With the RFC having been approved, it now raises the issue of how to represent the new optional namespace name in package names in Fedora. There was some discussion in the upstream ticket(s) about this, and I don't much like my conclusions - but here's a summary: - The only characters allowed in names of crates that are published on crates.io are a-z, A-Z, 0-9, hyphen, and underscore. These are all acceptable for RPM package names, which has allowed us to map "project published as $crate" -> "crate packaged as rust-$crate" without collisions (disregarding any possible collisions due to compat version suffices, which luckily has not happened yet). - The proposed separator between crate namespace and crate name is `::`(two colons, just like the import path separators in "use" statements in Rust code). This is not a valid character in RPM package names. - The intersection of the three sets "ascii characters", "characters that are valid in RPM package names", and "characters that cannot be part of a crate name" is vanishingly small. To the best of my knowledge, the intersection only contains two characters - the plus sign `+` and the dot `.`. - Rust crates as they are packaged in Fedora already use the `+` character as a separator for a different purpose in "feature subpackages'' (i.e. rust-$crate+$feature-devel), similarly to how Python packages handle "extras" with additional subpackages. As best as I can tell, this leaves us with only two options: The first option would be to adopt the `.` character as the separator character between crate namespace and crate name
[...]
The second option would be to "overload" the meaning of the `+` sign, and use it both as a separator between "crate namespace" and "crate name" *and* as the separator between "crate name" and "feature name". In this case, both the source package name and the binary package names will contain the `+` character. Using the `.` as the new separator, the source package names would not contain any `+` characters. However, this would not result in unambiguous package names in all cases (in particular, for "binary" packages).[...] I'm open to discuss other options, but I don't see any. Please let me know what you think.
Looks like one option would be to use ++, assuming feature subpackage names can't be empty.
FTR, other options are mentioned in the thread at https://github.com/rust-lang/rfcs/pull/3243#issuecomment-1807122869.
-- _______________________________________________ packaging mailing list -- packaging@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to packaging-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/packaging@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
