ValveSoftware / ValveSoftware/Proton

Reduce Proton installations across multiple steam libraries

Open
#2,242 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Feature Request
Dominant language
C++
Stars
32.8k
Forks
1.6k
PR merge metrics
PR metrics pending

Description

Feature Request

I confirm:

  • [x ] that I haven't found another request for this feature.
  • that I have checked whether there are updates for my system available that
    contain this feature already.

Description

Whilst performing some investigation for (https://github.com/ValveSoftware/Proton/issues/2241) I noticed that the same proton version was installed per steam library, rather than only once. Ideally, I only want one copy of proton 3.16-6 (or whatever other proton version I'm using) on my system.

As a manual fix I deleted most the Proton installations but, kept the copies residing under ~/.local/share/Steam/steamapps/common/ as that's my SSD and I have a need for speed. Then, I made symbolic links for Proton 3.7-8 / 3.16-4 / 3.16-6 to my other steam libraries across my HHD's and SSHD.

Justification [optional]

I don't not have my system WINE installed on each of my hard drives, it's installed once on my SSD. Why should proton be installed multiple times?

Risks [optional]

Reduced disk space usage.

References [optional]

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no source files, tests, or entry points. Begin by tracing how Proton versions are installed into the Steam library paths described in the report, with issue 2241 as related context; done means one Proton version is stored once and usable from multiple libraries without manual symlinks.

Written by the indexing model from the issue text.

Assessment

Domain
desktop, operating-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.