https://bugzilla.redhat.com/show_bug.cgi?id=1690046 --- Comment #6 from jogas@xxxxxxxx --- (In reply to Dave Love from comment #5) Once again thank you for your timely feedback. Below are answers to questions that were not addressed in the updated spec file. Spec file: https://copr-be.cloud.fedoraproject.org/results/jogas/charliecloud/fedora-rawhide-x86_64/00876701-charliecloud/charliecloud.spec SRPM: https://copr-be.cloud.fedoraproject.org/results/jogas/charliecloud/fedora-rawhide-x86_64/00876701-charliecloud/charliecloud-0.9.8-2.fc31.src.rpm > Why isn't there a doc package, as in Debian? The doc source has items which > aren't redundant with the man pages -- including about testing ... We plan to provide pre-built html files in the source tarball in an upstream release. > I think examples should be doc, though I don't think there are rules about > that. Both the example and test subdirectories are integral components of the test suite. It seems awkward to split the test suite into two packages, e.g., -doc and -test. That said, we do think the ‘examples’ directory name is somewhat misleading, especially considering how tightly coupled it is to the test suite. We plan to address this upstream in the near future. > It looks as if the test package should require docker (or maybe podman). The test suite runs and passes without Docker, the scope is just smaller. This is a situation we feel would benefit from debian-style package relationships, e.g., `recommends` or `suggests`. While we have do have tests that revolve around an image builder like Docker, Buildah, or Skopeo, the test suite does include tests that do not. > I assume you're trying to get sponsored, but I can't see a self-introduction > on the -devel list. I'm afraid I can't do it. I have not yet introduced myself to the -devel list. My focus has been to work with you to ensure we end up with a suitable package. That said, the goal is to become a fedora package manager, do you recommend I search for a sponsor in parallel? -- 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 _______________________________________________ package-review mailing list -- package-review@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to package-review-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/package-review@xxxxxxxxxxxxxxxxxxxxxxx
