add bin/gtuber-dl/gtuber-dl.1

[Rafostar]

Also, one thing I am concerned here with this MAN is that it will probably get outdated constantly. What tools did you use to generate it? Can we maybe generate up-to-date manual from within meson at/after compile? How other projects are handling this?

[josch]

I used help2man to generate this and then did some manual editing because the output wasn't very good yet. One of the problem is what I reported to GLib here: https://gitlab.gnome.org/GNOME/glib/-/issues/3007

But even after that is fixed, I would like to caution against using help2man because if help2man is required to build, then this will break cross-compilation because it will be necessary to run a foreign architecture binary to produce the man page.

Of course I can also understand the desire to never have the man page go out-of-sync with the program it is documenting. How about the following plan:

• use help2man to generate the man page but store its output in git
• then during the build process, if it's a native (not cross) build, use help2man to generate the man page and compare the result to the existing man page stored in git

That way, each (native) build will make sure that the man page is up-to-date while at the same time, cross builds will not need to re-generate the man page because it already exists.

What do you think?

[josch]

To avoid the dependency on help2man, GOptionContext could gain a new output format where instead of human-readable --help output, it would output in the roff format directly. I read glib/goption.c to create the patch I linked above and it seems that this would be quite a bit of work. And it also would not solve the problem with cross-compilation because it would also require running the binary.

[Rafostar]

How about storing this on git and making a git action that runs on git push, creates this file and if it differs it opens a MR with updated version?

[josch]

Sure, whatever works best for you! Though let me convert this pull request to a draft because:

• i've never written a github action creating a MR before
• before committing the man page to git, I'd like to add a short description and fix the encoding problem

[Rafostar]

• i've never written a github action creating a MR before

Oh, it does not need to be a part of this MR. I just want us to agree on something for now. If we determine that git action would be best, then no problem we can merge this as this action would replace this file anyway later. Just there won't be probably anyone to keep updating it manually until such solution exists.

• before committing the man page to git, I'd like to add a short description and fix the encoding problem

Yes, please do.

[sp1ritCS]

How about storing this on git and making a git action that runs on git push, creates this file and if it differs it opens a MR with updated version?

How about adding a git precommit hook that does the same (under the condition that the tool is installed) just without the extra MR?

[Rafostar]

How about adding a git precommit hook that does the same (under the condition that the tool is installed) just without the extra MR?

Also a nice idea. :+1: