When, for example, an .msi file is pushed using butler, it ends up:
as a single entry .zip, in the archive build file
as itself, the unpacked build file
up until now butler used to only use the archive build file, which means it extracted for installation, then realized what it had just "installed" was an .msi installer (or another kind of installer), and had to jump through all kinds of other hoops to make sure it's installed properly.
Having it use unpacked would allow it to do the install in a single step, instead of realizing its mistake later.
However, right now the API doesn't have a download url for unpacked, only for patch, signature and archive.
fasterthanlime
commented
6 years ago
When, for example, an .msi file is pushed using butler, it ends up:
archivebuild fileunpackedbuild fileup until now butler used to only use the
archivebuild file, which means it extracted for installation, then realized what it had just "installed" was an .msi installer (or another kind of installer), and had to jump through all kinds of other hoops to make sure it's installed properly.Having it use
unpackedwould allow it to do the install in a single step, instead of realizing its mistake later.However, right now the API doesn't have a download url for
unpacked, only forpatch,signatureandarchive.