[Feature Request] Local File Support for InstallerURL Property in Manifest File

[excelsi]

trafficstars

Description of the new feature / enhancement

I described the Feature here as an Issue: https://github.com/microsoft/winget-cli/issues/4358

Desired are local relative / full Paths for the InstallerURL Property in Package Manifest File like: ./Microsoft Visual Studio Code_1.88.0_User_X64_inno_en-US.exe (relative to the same Directory as the manifest file) and/or D:/TEMP/tempdown/Microsoft Visual Studio Code_1.88.0_User_X64_inno_en-US.exe and/or file://D:/TEMP/tempdown/Microsoft Visual Studio Code_1.88.0_User_X64_inno_en-US.exe

If the Feature Request is ok and its no Issue you can close the Issue.

Thanks!

Proposed technical implementation details

No response

[github-actions[bot]]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• [Feature Request] Allow winget manifests to use realitive paths. (#306), similarity score: 0.76

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[excelsi]

Any news on this? Thanks!

[denelon]

What scenario does this add value? Is this for "local" manifest validation, or something else where just running the local installer directly doesn't suffice?

[madcampos]

What scenario does this add value? Is this for "local" manifest validation, or something else where just running the local installer directly doesn't suffice?

For me, there is no installer, it is a zip file and I would like to take advantage of winget creating a nice entry to uninstall the program and adding links to PATH.

[excelsi]

What scenario does this add value? Is this for "local" manifest validation, or something else where just running the local installer directly doesn't suffice?

I have a local distribution Scenario without any internet access where a local Installer Path is needed. I also dont have a local Webserver in this case. But it still would be nice to use winget as Installer (with --manifest as local which works already).

[aserfass-msft]

In an offline scenario it would be nice to point to a local copy of the installer, validate the hash with winget, and install with winget (simplified commands). My team would also find this valuable.

A prime example would be run: "winget download <packageName>" then "winget install -m <yamlFileFromDownloadCommand>" If the generated yaml file referenced the local/relative file path that would enable many offline install scenarios

This feature would also make it much easier to upgrade/maintain apps offline

[excelsi]

@denelon Is there a possibility to get this feature or can't you spend any time on this? Thanks!

[denelon]

We're looking into the scenario for installing "offline" store packages. We'll need to extend the schema to add the license file to the manifest, and at that point, we'll look at options for referencing a "local" installer.

[excelsi]

We're looking into the scenario for installing "offline" store packages. We'll need to extend the schema to add the license file to the manifest, and at that point, we'll look at options for referencing a "local" installer.

Great thanks for the Feedback!