additional configurability of what gets installed #4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Do not try to build slimlock and install its manual page if it has been decided earlier not to. Typically this is the case when PAM is not used.
Allow not to install systemd related stuff (unit file) on Linux by setting HAVE_SYSTEMD=no during configuration time.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
while packaging SLiM on my Slackware system I have noticed, that an attempt is made to build
slimlockeven when PAM is disabled (which fails), and when that is worked around, the its manual page is installed regardless. Also systemd unit file is installed on Linux unconditionally which is not necessary right. The four commits are an attempt to fix these issues.Thank you
Kind regards
Petr