[Feature request]: A way to move app cache to RAM
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
The request concerns where Flatpak stores an app's cache and asks for a supported way to place it in RAM; it does not identify files, tests, or an implementation entry point. Start by reading how app caches are currently configured and why symlinking to /run/user/$UID/app was disabled for security reasons. Done means a safe, straightforward RAM-backed cache option is available; the issue does not specify its design.
Written by the indexing model from the issue text.
Description
Checklist
- I agree to follow the Code of Conduct that this project adheres to.
- I have searched the issue tracker for a feature request that matches the one I want to file, without success.
Suggestion
I used to symlink the app cache to /run/user/$UID/app (no permission changes needed), but it seems this was disabled in v1.18.1 or v1.19.0 for security reasons.
I'd like to request a straightforward method to move the app cache to RAM.
- Dominant language
- C
- Stars
- 5.1k
- Forks
- 526
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 23
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from flatpak/flatpak
-
[Feature request]: remove flatpak.fish completion so the shell's own completions are usedPossibly taken @Franklin-Qi claimed this 33 days ago. Openenhancement needs triage
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
[Feature request]: add support for `xdg-state` filesystem prefixPossibly taken @Franklin-Qi claimed this 33 days ago. Openenhancement libflatpak
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
flatpak/flatpak#5958 · 1 comment ·
Maintainers usually reply within 1 day
-
cli enhancement low priority
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Some flatpak repair strings are not translatableMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 Under an hour Newbie friendliness 65/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
stratum-mining/sv2-tp#167 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
libsdl-org/SDL_ttf#650 ·
-
HTTP Request Smuggling: non-final chunked Transfer-Encoding not rejected (CWE-444)Possibly taken @code1a2024 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
jaredgei/wow-forever-android#97 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
openziti/ziti-sdk-c#1254 ·
Maintainers usually reply within 1 day