Add receipt-only launch object messages #106
No reviewers
Labels
No labels
alpha-1
bug
ci
docs
duplicate
enhancement
help wanted
invalid
performance
phase-6
question
refactor
security
wontfix
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
erix/lib-ipc!106
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/receipt-only-launch-object-acquisition"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add dedicated V2 messages for receipt-only directory and resize-file acquisition.
Keep executable/manifest binding separate, accept complete raw selectors, and
correlate every reply with the original transaction, realm, scope and destination.
Failures carry no object evidence, including terminal destination conflicts.
Native adoption is coordinated with launchd#63
and vfsd#81.
Depends on #105.
WIP: Acquire receipt-only launch objectsto Add receipt-only launch object messagesThe message implementation is complete. Destination conflicts now use the existing checked result catalog and retain the same failure-field and correlation checks. Native consumer adoption remains coordinated through launchd#63 and vfsd#81.
Prepared the merge history at a34e0bd0 to remove duplicate upstream patches and integrate the feature on its prepared prerequisite history. The feature tree is unchanged.
The feature is reconciled with its current parent at
b34a8d043645c9be5f4ef9772f7b0af558762dd8onfeature/receipt-only-launch-object-acquisition-merge-ready-b34a8d04. The original work branch is preserved.This keeps the terminal launch-conflict fix and the maintained source policy without replaying shared CI commits. Descriptive selectors, entry digests and prompt text still confer no capability authority. Please review this exact commit; earlier approval does not cover the rewritten history.