[Feature Request] (core) (workflow) Pack resources before release and use packed res.
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.1k
- Forks
- 2.2k
- Avg merge
- 7h 35m
- Merged PRs (30d)
- 51
Description
Pack resources before release
RetroArch contains numerous small-block data assets, which slows down performance on HDD and reduces portability. Packing resources will simplify hashing and integrity checking if needed. Most modern devices will handle the additional load without issues. It might be possible to leave packing disabled only for weak and outdated devices and operating systems.
Many disks and file systems have increased cluster sizes, which is beneficial for game image collections but negatively affects data redundancy within clusters.
Benefits
- Improved performance on HDD.
- Enhanced portability.
- Simplified hashing and integrity checking.
Contributor guide
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
The issue names no files, tests, or release entry points. Start by locating RetroArch’s resource assets and release workflow, then determine how packing, portability, hashing, and weak-device behavior should be specified; done requires an agreed packing approach and its use before release.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- performance, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100