https://bugzilla.redhat.com/show_bug.cgi?id=2394287 --- Comment #4 from Carl George 🤠 <carl@xxxxxxxxxx> --- > At present, this package is indeed only providing an application. However, we intend to use it to revive the python-bloom package, which was retired from Fedora when "python-vcstools" (the third and oldest of these vcs utilities) was retired over a year ago due to abandonment upstream. To do that, Bloom will interact with vcs2l as a Python library. Thanks for the extra details about how it will be used. Regardless of the package name, it will have provides for python3dist(vcs2l) and python3.14dist(vcs2l), which should satisfy bloom's dependency as long as it's using the automatic dependency generator, so you could go a few different routes with the naming. It could just be just vcs2l (which will get the necessary provides), or python3-vcs2l (ideally providing vcs2l for discoverability). But I think for maximum correctness what I would suggest would be: * vcs2l source package * vcs2l subpackage (that depends on python3-vcs2l) with the commands and shell completions * python3-vcs2l subpackage with the library files > Indeed, but it required some cleanup that has yet to be released. I was planning on making the switch in the next version. > https://github.com/ros-infrastructure/vcs2l/pull/63 Ah, my mistake, I was viewing that test extra from the main branch where that PR is already merged. This recommendation can be deferred until the next version, or you could pull in that PR as a patch to take advantage of it now. Either way is fine. -- You are receiving this mail because: You are on the CC list for the bug. You are always notified about changes to this product and component https://bugzilla.redhat.com/show_bug.cgi?id=2394287 Report this comment as SPAM: https://bugzilla.redhat.com/enter_bug.cgi?product=Bugzilla&format=report-spam&short_desc=Report%20of%20Bug%202394287%23c4 -- _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-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/package-review@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue