Drop-OSS/drop
1
0
Fork 0
mirror of https://github.com/Drop-OSS/drop.git synced 2026-07-25 12:25:31 -04:00
Code Issues 77 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #225] Depots and installscripts #113

New Issue
Closed
opened 2026-02-17 17:06:11 -05:00 by yindo · 6 comments
yindo commented 2026-02-17 17:06:11 -05:00
Owner
Copy Link
Copy Source

Originally created by @zontreck on GitHub (Aug 30, 2025).
Original GitHub issue: https://github.com/Drop-OSS/drop/issues/225

Is your feature request related to a problem? Please describe.
Some games require redistributables, or a more complex setup process. So you might have the game setup, then a patch or two, in addition to required dependencies. Those dependencies could be in the form of a depot of sorts, a server-wide package that can be linked and downloaded/installed.

Describe the solution you'd like
I would like more control of the setup process. To be able to specify redistributables that are required, to be able to specify to run a setup, then patch 1 and/or 2. In that order, and to have the game expect to launch from the installed location. Now obviously the situation i described with packaging a setup and patches isn't ideal, you'd want to expand those first into their version folder. But, it was useful for detailing how much control i would like to have over the setup process.

Describe alternatives you've considered
None

Additional context
When installing a game from a platform like steam, they have a install script that is fairly dynamic, as well as global depots that developers can link to as required libraries. We should have that ability to make something similar.

Originally created by @zontreck on GitHub (Aug 30, 2025). Original GitHub issue: https://github.com/Drop-OSS/drop/issues/225 **Is your feature request related to a problem? Please describe.** Some games require redistributables, or a more complex setup process. So you might have the game setup, then a patch or two, in addition to required dependencies. Those dependencies could be in the form of a depot of sorts, a server-wide package that can be linked and downloaded/installed. **Describe the solution you'd like** I would like more control of the setup process. To be able to specify redistributables that are required, to be able to specify to run a setup, then patch 1 and/or 2. In that order, and to have the game expect to launch from the installed location. Now obviously the situation i described with packaging a setup and patches isn't ideal, you'd want to expand those first into their version folder. But, it was useful for detailing how much control i would like to have over the setup process. **Describe alternatives you've considered** None **Additional context** When installing a game from a platform like steam, they have a install script that is fairly dynamic, as well as global depots that developers can link to as required libraries. We should have that ability to make something similar.
yindo added the featureconfirmedduplicate labels 2026-02-17 17:06:11 -05:00
yindo commented 2026-02-17 17:06:11 -05:00
Author
Owner
Copy Link
Copy Source

@mavanmanen commented on GitHub (Sep 1, 2025):

I think you would be able to do this using a batch script, at least in the context of single games and it's patches and/or redistributables.

@mavanmanen commented on GitHub (Sep 1, 2025): I think you would be able to do this using a batch script, at least in the context of single games and it's patches and/or redistributables.
yindo commented 2026-02-17 17:06:11 -05:00
Author
Owner
Copy Link
Copy Source

@zontreck commented on GitHub (Sep 1, 2025):

i think you do not understand my suggestion.

Sep 1, 2025 2:48:01 AM Mitchell van Manen @.***>:

 [Image]*mavanmanen* left a comment (Drop-OSS/drop#225)[https://github.com/Drop-OSS/drop/issues/225#issuecomment-3241663396]

I think you would be able to do this using a batch script, at least in the context of single games and it's patches and/or redistributables.

—
Reply to this email directly, view it on GitHub[https://github.com/Drop-OSS/drop/issues/225#issuecomment-3241663396], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAMRK2XK3YBZ7XVCZZJJRHD3QQI5DAVCNFSM6AAAAACFHKBSS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENBRGY3DGMZZGY].
You are receiving this because you authored the thread.
[Tracking image][https://github.com/notifications/beacon/AAMRK2U5KU4XAKNVZPHLBTL3QQI5DA5CNFSM6AAAAACFHKBSS2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTWBG7N2I.gif]

@zontreck commented on GitHub (Sep 1, 2025): i think you do not understand my suggestion. Sep 1, 2025 2:48:01 AM Mitchell van Manen ***@***.***>: > > [Image]*mavanmanen* left a comment (Drop-OSS/drop#225)[https://github.com/Drop-OSS/drop/issues/225#issuecomment-3241663396] > > > I think you would be able to do this using a batch script, at least in the context of single games and it's patches and/or redistributables. > > — > Reply to this email directly, view it on GitHub[https://github.com/Drop-OSS/drop/issues/225#issuecomment-3241663396], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AAMRK2XK3YBZ7XVCZZJJRHD3QQI5DAVCNFSM6AAAAACFHKBSS2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTENBRGY3DGMZZGY]. > You are receiving this because you authored the thread. > [Tracking image][https://github.com/notifications/beacon/AAMRK2U5KU4XAKNVZPHLBTL3QQI5DA5CNFSM6AAAAACFHKBSS2WGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTWBG7N2I.gif] >
yindo commented 2026-02-17 17:06:11 -05:00
Author
Owner
Copy Link
Copy Source

@mavanmanen commented on GitHub (Sep 1, 2025):

I do, but my solution is only to address part of your intention. It excludes being able to create a depot with shared distributables.

@mavanmanen commented on GitHub (Sep 1, 2025): I do, but my solution is only to address part of your intention. It excludes being able to create a depot with shared distributables.
yindo commented 2026-02-17 17:06:11 -05:00
Author
Owner
Copy Link
Copy Source

@lavabrothers commented on GitHub (Oct 6, 2025):

I want to add, it maybe easier to allow for non-executable steps in the install scripts on linux. For Linux deployments that use umu-launcher on windows games, some times you will need to install dependencies such as mono or dx9.

This can be solved by running umu-run winetricks d3dx9 dotnet40 assuming you want to install into the default prefix. Maybe in the advanced options where you can add a wintricks setup step. Or as Mavanmanen said a batch/bash script so we can run commands to install dependencies.

Typically this can be accomplished is the umu-database as the desired gameid noted for specific patches, but for games that aren't in the database or won't be added we are SOL without having linux users run a command themselves for their randomized/custom prefix

This is kinda like a depot since you would be sourcing from the winetricks depot of dependencies, but doesn't help pure windows users who don't use wine

I think simply we can decouple the setup from needing an executable, as right now you need to provide an executable for the setup step to be performed (at least in my testing). And if you provide a bash script it tried to run with umu-run which fails.

Or maybe drop can ship a premade prefix for installation?

@lavabrothers commented on GitHub (Oct 6, 2025): I want to add, it maybe easier to allow for non-executable steps in the install scripts on linux. For Linux deployments that use umu-launcher on windows games, some times you will need to install dependencies such as mono or dx9. This can be solved by running `umu-run winetricks d3dx9 dotnet40` assuming you want to install into the default prefix. Maybe in the advanced options where you can add a wintricks setup step. Or as Mavanmanen said a batch/bash script so we can run commands to install dependencies. Typically this can be accomplished is the umu-database as the desired gameid noted for specific patches, but for games that aren't in the database or won't be added we are SOL without having linux users run a command themselves for their randomized/custom prefix This is kinda like a depot since you would be sourcing from the winetricks depot of dependencies, but doesn't help pure windows users who don't use wine I think simply we can decouple the setup from needing an executable, as right now you need to provide an executable for the setup step to be performed (at least in my testing). And if you provide a bash script it tried to run with umu-run which fails. Or maybe drop can ship a premade prefix for installation?
yindo commented 2026-02-17 17:06:11 -05:00
Author
Owner
Copy Link
Copy Source

@lavabrothers commented on GitHub (Nov 3, 2025):

For anybody looking back and no solution has been developed yet, I have found using a bat script with all the c++ runtimes needed does work. For Linux users it works very well. Here is a script and redistributables for visual c++, which is often the main required dlls for games

https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/

Since this has the all the executables together, its 100mbs worth of space. So it maybe a good idea to centralize them as zontreck mentions

@lavabrothers commented on GitHub (Nov 3, 2025): For anybody looking back and no solution has been developed yet, I have found using a bat script with all the c++ runtimes needed does work. For Linux users it works very well. Here is a script and redistributables for visual c++, which is often the main required dlls for games https://www.techpowerup.com/download/visual-c-redistributable-runtime-package-all-in-one/ Since this has the all the executables together, its 100mbs worth of space. So it maybe a good idea to centralize them as zontreck mentions
yindo changed title from Depots and installscripts to [GH-ISSUE #225] Depots and installscripts 2026-06-05 14:21:30 -04:00
yindo closed this issue 2026-06-05 14:21:30 -04:00
yindo commented 2026-06-05 14:21:31 -04:00
Author
Owner
Copy Link
Copy Source

@DecDuck commented on GitHub (Feb 18, 2026):

The infrastructure for this will land in v0.4.0, but I'm not sure the UI/configuration will land with it, likely in v0.4.1.

<!-- gh-comment-id:3919402722 --> @DecDuck commented on GitHub (Feb 18, 2026): The infrastructure for this will land in v0.4.0, but I'm not sure the UI/configuration will land with it, likely in v0.4.1.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
duplicate
feature
feature
good first issue
needs-triage
pull-request
Mirrored from GitHub Pull Request
 qol
support
No Label confirmed duplicate feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Drop-OSS/drop#113
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?