Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Deleting manpage markdown leave roff behind #4542

Closed
kodebach opened this issue Oct 12, 2022 · 15 comments
Closed

Deleting manpage markdown leave roff behind #4542

kodebach opened this issue Oct 12, 2022 · 15 comments

Comments

@kodebach
Copy link
Member

Our manpages are written as markdown in doc/help and then converted to roff and stored in doc/man. Since doc/man is also committed to the repo, the folders have to be kept in sync. We have a CI job that checks that all files have been generated. But if a file is deleted from doc/help there is nothing that ensures the file is also deleted from doc/man.

Ideally, the old file would be deleted from doc/man automatically during the build. But there should at least be a CI job that checks that we don't have roff files without markdown sources.

@kodebach

This comment was marked as off-topic.

@atmaxinger
Copy link
Contributor

On a related note, why do we have to keep the man pages committed in the repository?

@kodebach
Copy link
Member Author

AFAIK it is so Elektra can be built (including full docs) without the somewhat obscure ronn-ng tool.

@atmaxinger

This comment was marked as off-topic.

@kodebach

This comment was marked as off-topic.

@markus2330

This comment was marked as off-topic.

@kodebach

This comment was marked as off-topic.

@markus2330

This comment was marked as off-topic.

@kodebach

This comment was marked as off-topic.

@markus2330
Copy link
Contributor

Thank you, yes let us focus on the main point. It is suitable for FLOSS. The same is true for checking if Doxygen might work as alternative. I created #4551.

Let us please avoid such unstructured discussions about "Why?" in the future (now hidden above), as it takes our precious time and, without a decision as result, doesn't lead anywhere. I added the current status as draft decision "manpages.md" in #4528, so that this decision is not lost (again).

@kodebach

This comment was marked as off-topic.

@markus2330

This comment was marked as off-topic.

@atmaxinger
Copy link
Contributor

One final note from me - my question was meant to reevaluate whether the issue brought up here is actually an issue. If we dont check in the man pages there is no Need to keep them in sync.

@flo91 flo91 changed the title Deleting manpage markdown leave roff behind [FLOSS] Deleting manpage markdown leave roff behind Oct 18, 2022
@flo91 flo91 changed the title [FLOSS] Deleting manpage markdown leave roff behind Deleting manpage markdown leave roff behind Oct 18, 2022
@github-actions
Copy link

I mark this stale as it did not have any activity for one year. I'll close it in two weeks if no further activity occurs. If you want it to be alive again, ping by writing a message here or create a new issue with the remainder of this issue.
Thank you for your contributions 💖

@github-actions github-actions bot added the stale label Oct 19, 2023
Copy link

github-actions bot commented Nov 5, 2023

I closed this now because it has been inactive for more than one year. If I closed it by mistake, please do not hesitate to reopen it or create a new issue with the remainder of this issue.
Thank you for your contributions 💖

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants