While there are ways to set the original nupkg (with the version on it, not the one in the packages directory - use download from left side of packages page on the Chocolatey community package repository) and preset the downloaded binaries into the cache folder, it's not always deterministic that it will work. This is not a limitation when using Chocolatey internally. Typically package maintainers on the community package repository do not have distribution rights for the actual software binaries, so the package needs instructions to go download those resources and act on them. You can do this manually or look at Chocolatey for Business to do this. We've updated this question based on content at Sources can be one of the following formats: Will research it further.įirst let's address a misconception. My experience with Homebrew gives me a clue that if Chocolatey stores the downloaded packages, I could just manually take them from the storage path on one PC and put to that path on the other one. Running a server for a single use is an overkill for this task.
However, it expects a URL and not a local path. UPD: Probably there's a way to achieve this by using a custom nfig, where I explicitely change source. So, is there a way to do such a trick with chocolatey? But there are quite a lot packages (around 20) and I really, really like the UNIX way of doing things. Yes, I could just download installers one-by-one and then install them consecutively. I'd like to download a bunch of chocolatey packages and later install them on another PC (which has a bad internet connection, so I cannot just install them in a usual way).
0 kommentar(er)
