Thanks for that link, I’ve wondered that myself at times.
I’m maintaining one chocolately package and I think I’ve already run into one of these but I’m also not sure if scoop’s solution is better. (User-installed JDK versus depending on it to be seperately installed)
Eh, just another SETUP.EXE downloader; I can do that myself. What’d be useful is actual package management with proper dependency resolution and fetching on Windows. Unfortunately, it’s something I haven’t seen. (I think Windows Installer /has/ the backend bits; so something like an apt-msi is possible, but…)
Neat. I wondered how this was different from Chocolatey, and found https://github.com/lukesampson/scoop/wiki/Chocolatey-Comparison
Thanks for that link, I’ve wondered that myself at times. I’m maintaining one chocolately package and I think I’ve already run into one of these but I’m also not sure if scoop’s solution is better. (User-installed JDK versus depending on it to be seperately installed)
Eh, just another
SETUP.EXEdownloader; I can do that myself. What’d be useful is actual package management with proper dependency resolution and fetching on Windows. Unfortunately, it’s something I haven’t seen. (I think Windows Installer /has/ the backend bits; so something like anapt-msiis possible, but…)I built an apt clone that worked on Windows once, but we never got past proof of concept
I assume this is the Windows equivalent of piping the output of curl to the shell. Boo.