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

[QUESTION] Should habitat packages support man pages? #2500

Closed
ghost opened this issue May 30, 2017 · 4 comments
Closed

[QUESTION] Should habitat packages support man pages? #2500

ghost opened this issue May 30, 2017 · 4 comments

Comments

@ghost
Copy link

ghost commented May 30, 2017

Very similar to the helper methods such as pkg_bin_dirs, should a similar construct be created to support man page entries?

The thought process is the following ....

I agree that runtime environments probably do not need things such as man pages but if that is the case, they should be stripped out of the build and maybe this is an issue against the core-plans repository ....

That being said, it would be interesting to see that is man is on the path, the man packages would optionally be installed and could be determined by another helper utility such as pkg_man_dirs ...

@reset
Copy link
Collaborator

reset commented Jul 27, 2017

I think we should add this support but we need to think a bit on how we figure out which man pages we should show you. Perhaps this is part of the binlink process?

@skull-squadron
Copy link

skull-squadron commented May 22, 2019

Just encountered this issue:

  • Perhaps hab [pkg {{package_name}}] man [{{section}}] {{what}}
  • Generate a man.conf dynamically that adds MANPATH {{each of pkg_man_dirs}} (hab man ... should look at binlinked packages, hab pkg {{package_name}} man ... should look at specific package's man page)
  • Then passed on to the underlying man (man [{{section}}] {{what}} -C /path/to/temp/man.conf)
  • Also, during packaging, included man pages should always be compressed.

@stale
Copy link

stale bot commented May 21, 2020

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. We value your input and contribution. Please leave a comment if this issue still affects you.

@stale stale bot added the Stale label May 21, 2020
@stale
Copy link

stale bot commented Jun 25, 2021

This issue has been automatically closed after being stale for 400 days. We still value your input and contribution. Please re-open the issue if desired and leave a comment with details.

@stale stale bot closed this as completed Jun 25, 2021
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