Closed rwarren closed 5 years ago
scoop installs the program with ZIP file of "without JVM" version, which does not contain JVM.
I think it would be better to choose the "with JVM" version (it will be more stable and less likely to have problems). However, the installer of dbvis
modifies Windows Registry (which is against the general criteria of scoop).
If we can "crack open" the installer and extract all the required files from it, we can add it to scoop, but the installer is made with install4j
, and I can't find a way to do that.
If dbvis depends on java, just install java with scoop. And add
"suggest": {
"JDK": [
"java/oraclejdk",
"java/openjdk"
]
}
in manifest.
However, the installer of
dbvis
modifies Windows Registry (which is against the general criteria of scoop).If we can "crack open" the installer and extract all the required files from it, we can add it to scoop, but the installer is made with install4j, and I can't find a way to do that.
Hello,
I have a similar problem and would like to know how you resolved this. In dbvis.json, I see this:
"extract_dir": "DbVisualizer",
"bin": [
"dbvis.exe",
"dbviscmd.bat"
],
Is this it? How do you handle Windows registry modifications then? Or are apps that really rely on this, out of scoop's scope?
scoop install dbvis
installs correctly (see below), but when you try and run it you get "No JVM could be found on your system". The application should be self contained, not require Java knowledge to get it working.A successful install:
What happens when you run it: