Include generated manual page in the repository? about dog HOT 3 OPEN

Cheers! And thanks for dealing with the packaging side of things for me.

This was something on my mind when I switched from writing the man page in troff directly to writing it in Markdown — it was way easier to update, but at the cost of a big build dependency. I figured that including the generated man page in the release zip would be enough, but it looks like you're building from source.

I'm hesitant to include the man page in the repo because I've seen built files go out-of-date before, but I can do it if there's no other option. Do you know if there's a way in Nix to get the man page and completions from a release artifact like that? If you don't want to download a compiled binary you won't end up using, I could upload another zip that only contains the OS-independent files (called "contrib" or something)

from dog.

Do you know if there's a way in Nix to get the man page and completions from a release artifact like that? If you don't want to download a compiled binary you won't end up using, I could upload another zip that only contains the OS-independent files (called "contrib" or something)

We could take them from release artifacts, but a contrib zip would be really nice, since it saves some bandwidth.

from dog.

???????????????????????????????????????????????????????????????????????????????????????????????????????????????????

from dog.