Parse PKGINFO once and reuse parsed structure everywhere #2002
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
markusthoemmes
force-pushed
the
parse-pkginfo-once
branch
3 times, most recently
from
cf67e26 to
9e56779
Compare
Instead of reparsing PKGINFO from the control filesystem over and over again, this does it once and as a tested helper on APKExpanded. Behavior is the same as before with the difference of using `SplitN` over `Split` to not have a buggy example.
markusthoemmes
force-pushed
the
parse-pkginfo-once
branch
from
965c5a7 to
2018e0c
Compare
imjasonh
approved these changes
Jan 12, 2026
kevinmdavis
approved these changes
Jan 12, 2026
jonjohnsonjr
approved these changes
Jan 12, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Instead of reparsing PKGINFO from the control filesystem over and over again, this does it once and as a tested helper on APKExpanded.
Intention is that the behavior stays the same, effectively, even though the parsing is done somewhat differently.