On Mon, 9 Sep 2024 14:00:56 +0300 Faidon Liambotis <parav...@debian.org> wrote: > On Sun, Sep 01, 2024 at 01:08:07PM +0100, James Addison wrote: > > I'd like to request that we ship the upstream libpod manual[1] instead, and > > optionally that we could retain the podman-compose version of the manual in > > section 7 (misc). Most installers of podman-compose would be provided with > > the > > libpod manual thanks to the Recommends dependency that podman-compose has on > > libpod.
>From an user's point of view, I'd rather have them the other way around. Upstream podman manual is just a manual telling users its subcommand does nothing but forwarding the command to an external composer (with a given precedence), and instructing on how to disable the warning. Debian's manual page for podman-compose itself should be more meaningful as a "Executable programs or shell commands" (section 1) manual page. (Although it is currently only a help2man generated page.) Also, this makes more convenient for users, since section 1 has precedence by default over section 7. Doing so would require shipping it as a section 7 manpage, and patching podman source to make messages consistent. I'm afraid upstreaming this might not make sense, though, as podman-compose does not want to maintain a manual page yet [1]; thus no conflict actually exists upstream (yet). Well, this should be way more work to do, though. It would also mean taking care of yet another patch in podman package. It is understandable if it is chosen not to. [1] https://github.com/containers/podman-compose/pull/481 > I actually agree with this, and was also bitten by it recently! It's > worth noting that podman-compose upstream does not ship a manpage at all > -- this is a Debian modification and divergence from upstream. > > For podman to ship this manpage again, podman-compose needs to stop > shipping it, so reassigning the bug to the podman-compose source > package. > > Athos & other podman-compose contributors, what do you think? I'm not a podman-compose contributor myself, but I hope you find my comments useful. Best regards, Henrique F. Simoes
