Process doesn't show up with Scoop install script #5641
Unanswered
EstebanMunoz
asked this question in
Help and Questions
Replies: 1 comment 1 reply
-
You could try storing the output of the |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi guys, I'm trying to write a manifest to install Battle.net, but since there is no switch for the installer I relied on the processes instead (so it should be a non-portable app). The thing is, first I wrote a simple script that starts a loop waiting for a process called
Battle.net-Setup
to appear, and after that checks if a second process calledBattle.net
started. If one of these conditions failed, the script prints Error (could raise an error but this is just a naive test).The script below needs admin rights.
When I put the script in a Scoop manifest the process
Battle.net-Setup
never shows up. I guess everything is getting done by other process that shows up calledAgent
(which also appears when the script is not inside the manifest). The problem with this behavior (aside from wondering why is this happening) is that I don't know when to look for theBattle.net
process, which is only started if the app has been successfully installed. Such behavior is important since there is no easy way to hide the installer window, and the user could potentially cancel the installation. When this happens, the Battle.net process is not started and an error is raised. This is also useful in the cases in which the installer doesn't start the installation and instead displays some "Try again" window, resulting in the Battle.net process not initializing.The other process (
Agent
) doesn't stop when the installation is done, so at this point I don't know what to do. I'm open to ideas and improvements, thank you guys in advance.Beta Was this translation helpful? Give feedback.
All reactions