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

Please allow enabling/disabling manpages and docs separately with individual --enable-xx arguments #3378

Open
yurivict opened this Issue Aug 30, 2018 · 6 comments

Comments

Projects
None yet
4 participants
@yurivict

yurivict commented Aug 30, 2018

I'm submitting a…

[ ] Bug
[X] Feature Request
[ ] Documentation Request
[ ] Other (Please describe in detail)

Current Behavior

Can't leave manpages and remove docs

Expected Behavior

Need to be able to enable docs independently from manpages.
Please have separate enable/disable arguments for both.

Reason

In the FreeBSD port we need to be able to enable/disable manpages and docs separately, because they are separate port options.

Version 4.15.0.1 on FreeBSD.

@i3bot i3bot added the enhancement label Aug 30, 2018

@yurivict yurivict changed the title from Please allow enabging/disabling manpages and docs separately with individual --enable-xx arguments to Please allow enabling/disabling manpages and docs separately with individual --enable-xx arguments Aug 30, 2018

@Airblader

This comment has been minimized.

Show comment
Hide comment
@Airblader

Airblader Sep 3, 2018

Member

There's a port for vanilla i3 AFAIK, so my main question would be why the i3-gaps port needs this if the i3 port doesn't? Can you answer that or involve the maintainer of the i3 port for this?

Member

Airblader commented Sep 3, 2018

There's a port for vanilla i3 AFAIK, so my main question would be why the i3-gaps port needs this if the i3 port doesn't? Can you answer that or involve the maintainer of the i3 port for this?

@yurivict

This comment has been minimized.

Show comment
Hide comment
@yurivict

yurivict Sep 3, 2018

They both need this. All ports need to be able to control manpages and docs separately.

yurivict commented Sep 3, 2018

They both need this. All ports need to be able to control manpages and docs separately.

@Airblader

This comment has been minimized.

Show comment
Hide comment
@Airblader

Airblader Sep 3, 2018

Member

OK then. Can we get the maintainer of that port involved then so that they're aware of this?
As for the request itself: sounds good to me, PRs welcome.

Member

Airblader commented Sep 3, 2018

OK then. Can we get the maintainer of that port involved then so that they're aware of this?
As for the request itself: sounds good to me, PRs welcome.

@yurivict

This comment has been minimized.

Show comment
Hide comment
@yurivict

yurivict Sep 3, 2018

I'm not a maintainer of either of them.

yurivict commented Sep 3, 2018

I'm not a maintainer of either of them.

@Airblader

This comment has been minimized.

Show comment
Hide comment
@Airblader

Airblader Sep 3, 2018

Member

So can we get both of them involved, then? I'm guessing a change in i3 is a bit pointless if the ports won't adapt it.

Member

Airblader commented Sep 3, 2018

So can we get both of them involved, then? I'm guessing a change in i3 is a bit pointless if the ports won't adapt it.

@yurivict

This comment has been minimized.

Show comment
Hide comment
@yurivict

yurivict Sep 3, 2018

The more people are involved, the lower the chance of something to be successful.
Of course it will be adopted, I will submit a patch and they will likely adopt it.

yurivict commented Sep 3, 2018

The more people are involved, the lower the chance of something to be successful.
Of course it will be adopted, I will submit a patch and they will likely adopt it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment