[Feature Request] add flag to disable automatic updates during build #234

Closed
opened 2026-04-05 16:16:53 +02:00 by MrUnknownDE · 0 comments
Owner

Originally created by @kazu0617 on 11/3/2025

Explain in detail what your suggested feature would be used for.
When installing VRCX through a package manager (apt, yum, or paru), if VRCX performs a self-update, it may create version inconsistencies between the actual VRCX installation and the version reported by the package manager.

Currently we're addressing this issue by applying patches to related update displays and update processes, but it would be greatly appreciated if we could control this behavior through build flags.

Describe how it would look if it requires a UI.

All images and information are for testing purposes. While more appropriate displays exist, one example follows:

Image Image

Explain why people would want to use it.

To reduce confusion...? To avoid being managed twice by both self-updates and package manager updates.
Originally, I didn't plan to file an issue because this was purely a matter of convenience for the package maintainers, including myself.
However, since someone in the VRCX PR was proposing changes based on patches I had written, filing this issue also serves to reduce such potential confusion.

*Originally created by @kazu0617 on 11/3/2025* **Explain in detail what your suggested feature would be used for.** When installing VRCX through a package manager (apt, yum, or paru), if VRCX performs a self-update, it may create version inconsistencies between the actual VRCX installation and the version reported by the package manager. Currently we're addressing this issue by applying patches to related update displays and update processes, but it would be greatly appreciated if we could control this behavior through build flags. **Describe how it would look if it requires a UI.** All images and information are for testing purposes. While more appropriate displays exist, one example follows: <img width="1147" height="924" alt="Image" src="https://github.com/user-attachments/assets/80f29983-2ca9-4e42-a410-64d2a1776e03" /> <img width="1147" height="924" alt="Image" src="https://github.com/user-attachments/assets/db64dc07-ff3c-48b8-a8fc-e87977483d5c" /> **Explain why people would want to use it.** To reduce confusion...? To avoid being managed twice by both self-updates and package manager updates. Originally, I didn't plan to file an issue because this was purely a matter of convenience for the package maintainers, including myself. However, since someone in the VRCX PR was proposing changes based on patches I had written, filing this issue also serves to reduce such potential confusion.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github/VRCX#234