[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.
[X] I have verified that I am using the latest version of Scoop and corresponding bucket.
Package Name
openssl
Expected/Current Behaviour
Scoop appears to be installing the large ~200MB behemoth installers without paying attention to whether or not the user actually needs it. Unless the user is writing software (i.e. they are using Visual C++), they almost certainly do not need the full installer packages, which contain everything output from the build process that a developer might need (libraries, header files, test/validation EXEs, etc).
In addition, Scoop appears to make multiple simultaneous requests for parts of files, which creates an additional burden on infrastructure, especially when hosting large files.
Steps to Reproduce
scoop install main/openssl
Possible Solution
Please rename the openssl package to openssl-dev (or openssl-devel or openssl-developer) to give an indication that the package is only intended for software developers working directly with the library in their C/C++ software applications. Maybe also consider moving "versions/openssl-light" to main and further consider moving "main/openssl-dev" to versions. Essentially the inverse of what's happening now with a better naming scheme so that most users are not wasting their time nor terabytes of network transfer. While I'm pretty sure most Scoop users at this point are software developers based on communications I've had, it does appear to be changing to some degree.
Alternatively, you could host a mirror for your users for all packages in main so that your users aren't requesting from origins.
Scoop could also benefit from a WSUS-like deployment tool for multiple users/machines on an internal network if it doesn't have one already.
Prerequisites
Package Name
openssl
Expected/Current Behaviour
Scoop appears to be installing the large ~200MB behemoth installers without paying attention to whether or not the user actually needs it. Unless the user is writing software (i.e. they are using Visual C++), they almost certainly do not need the full installer packages, which contain everything output from the build process that a developer might need (libraries, header files, test/validation EXEs, etc).
In addition, Scoop appears to make multiple simultaneous requests for parts of files, which creates an additional burden on infrastructure, especially when hosting large files.
Steps to Reproduce
Possible Solution
Please rename the openssl package to openssl-dev (or openssl-devel or openssl-developer) to give an indication that the package is only intended for software developers working directly with the library in their C/C++ software applications. Maybe also consider moving "versions/openssl-light" to main and further consider moving "main/openssl-dev" to versions. Essentially the inverse of what's happening now with a better naming scheme so that most users are not wasting their time nor terabytes of network transfer. While I'm pretty sure most Scoop users at this point are software developers based on communications I've had, it does appear to be changing to some degree.
Alternatively, you could host a mirror for your users for all packages in main so that your users aren't requesting from origins.
Scoop could also benefit from a WSUS-like deployment tool for multiple users/machines on an internal network if it doesn't have one already.
Scoop and Buckets Version
Scoop Config
PowerShell Version
Additional Softwares
No response