microsoft / microsoft/msix-packaging
Feature request - unpack needs single-file / footprint-file option
Open
Nobody has claimed this yet.
Area-MSIX SDK
Feature
- Dominant language
- C
- Stars
- 1.1k
- Forks
- 193
- Avg merge
- 2h 16m
- Merged PRs (30d)
- 2
Description
Unpacking a multi-mb/multi-gb MSIX to pull out one file is wasteful. Please include a "-f" and "-ff" option, like:
# Unpack just the muffin.wasm and a group of DLLs
makemsix unpack -p file.msix -d .\output -ss -f code-assets\muffin.wasm -f appsvcimpl\*.dll
# Unpack just the catalog and manifest
makemsix unpack -p file.msix -d .\output -ss -ff codeintegrity -ff manifest
Where the "-ff" options are for the footprint files.
| Option | File |
|---|---|
| manifest | The AppXManifest.xml for the package |
| blockmap | The blockmap XML file |
| signature | The signature file, if present |
| codeintegrity | The catalog file, if present |
| contentgroupmap | The content group map file |
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file or test is named. Start at the makemsix unpack command and review how MSIX files and footprint files are selected; done means -f accepts individual or wildcard paths and -ff selects the listed footprint types, with the examples working without unpacking unrelated files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100