xbps-triggers: Add *_uname variable for system_accounts#61273
Open
oreo639 wants to merge 1 commit into
Open
Conversation
Account names may require characters such as dashes, however these characters are not legal as bash variables. This works around the issue by allowing you to do: system_accounts="myaccount" gdmgreeter_name="my-account" gdmgreeter_pgroup="my-account"
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Account names may require characters such as dashes, however these characters are not legal as bash variables.
This works around the issue by allowing you to do: system_accounts="myaccount"
gdmgreeter_name="my-account"
gdmgreeter_pgroup="my-account"
A real-world example is present with gdm 49+, which depends on a user named gdm-greeter.
This PR allows for the gdm-greeter account (and successfully loading into gdm 49+) as seen here: oreo639@86188bd
Let me know if there is a better way to handle this.
Testing the changes