fix(pkg): compare compiler packages semantically - #16173
Draft
Alizter wants to merge 1 commit into
Draft
Conversation
Alizter
added
package management
Alizter
force-pushed
the
push-qvromqwnysom
branch
from
August 24, 2026 13:02
b3cddd3 to
9b7a531
Compare
Alizter
force-pushed
the
push-qvromqwnysom
branch
from
August 24, 2026 15:15
9b7a531 to
e01ff8f
Compare
Compare compiler package data after selecting current-platform conditional fields and stripping parser source locations. This reuses an unchanged dev-tool lock while still relocking for same-version recipe changes. Signed-off-by: Ali Caglayan <alizter@gmail.com>
3 tasks
Alizter
force-pushed
the
push-qvromqwnysom
branch
from
August 25, 2026 13:00
e01ff8f to
b965c26
Compare
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
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.
Description
Compare the project and dev-tool compiler packages after selecting their current-platform conditional fields and removing parser source locations.
This allows an unchanged effective compiler package to reuse its existing dev-tool lock directory while still relocking when the compiler recipe changes without a version bump. The diagnostic now distinguishes a same-version package change from an actual compiler version change.
The regression test merged in #16168 uses a sentinel to distinguish lock-directory reuse from identical regeneration and verifies that a same-version recipe change still triggers relocking.
Relationship to other package changes
This PR is based directly on
main. It is independent of the joint-platform solver in #15982 and the lock-stanza environment fix in #16172; all three can be reviewed and landed independently.Related Issue and Motivation
Follow-up to #16168. Structural package equality treated representation details and parser locations as package changes, causing unnecessary dev-tool relocking.
Checklist