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

Additions for compiling plymouth #1312

Merged
merged 4 commits into from
Mar 22, 2025
Merged

Additions for compiling plymouth #1312

merged 4 commits into from
Mar 22, 2025

Conversation

no92
Copy link
Member

@no92 no92 commented Mar 20, 2025

No description provided.

Copy link
Contributor

@mintsuki mintsuki left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See comments

@no92
Copy link
Member Author

no92 commented Mar 20, 2025

Fixed comments + provided a test for rpmatch.

@mintsuki mintsuki added this pull request to the merge queue Mar 20, 2025
@mintsuki mintsuki removed this pull request from the merge queue due to a manual request Mar 20, 2025
return 0;
if(resp[0] == 'y' || resp[0] == 'Y')
return 1;
if(resp[0] == 'n' || resp[0] == 'N')
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

rpmatch shouldn't really accept something like yno and interpret it as yes... so these checks should probably be inlined with the prior strcasecmps. eg:

if(!strcasecmp("yes", resp) || !strcasecmp("y", resp))

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It should, and the man page specifically mentions this.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Where does it say that? Because i can't find it.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

afaict it just says you have to match ^[Yy] and ^[Nn] regardless of language, not ^[Yy].* or ^[Nn].*

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

^[Yy] and ^[Nn] don't match whole strings, they match anything that starts with Y/y/N/n.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

okay, that being the case I think this is stupid behaviour that we should not be emulating

@no92
Copy link
Member Author

no92 commented Mar 21, 2025

Updated to apply fixes.

@mintsuki mintsuki enabled auto-merge March 22, 2025 07:47
@mintsuki mintsuki added this pull request to the merge queue Mar 22, 2025
Merged via the queue into managarm:master with commit 54d5c81 Mar 22, 2025
38 checks passed
@no92 no92 deleted the plymouth branch March 22, 2025 11:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants