How often do I need to do: winget configure .config/configuration.winget ?

[AltitudeApps]

Is this a system-wide configuration that I only need to do once, or is it something I need to do in every repo checkout folder?

I have multiple versions of the working copy of the repo on my machine, because I can build the one I checked out on March 31st, but I have some more recent versions of the source tree which are not working yet. I'm working my way forwards from the 6096b5e commit, checking out more recent commits to their own folders, so find out when things break for me.

[mdanish-kh]

The configurations are idempotent - meaning they always check your current system system before "applying" any configuration. This means, you only ever have to run it once if your system lacks the configuration where WinGet will get it in the "desired state" (i.e., installing dependencies, enabling developer mode & others specified in the file). Afterwards, you can run the configuration as many time you want and it should essentially have "no effect" as it will assert your system already being in the desired state.

What this means is that you don't necessarily have to run it for every repo checkout - but if somehow the dependencies or the configs are missing, running it again will get you back in the desired state.

[AltitudeApps]

Thank you, that's what I wanted to know. It's a "One and (probably, for now...) Done" situation.

Thank you very much.

I have some further questions, but I'm waiting on some build output to see what is failing, and under what circumstances.

[AltitudeApps]

I'm still having difficulties. I posted about it here:

#5394

[denelon]

I'll ask an engineer to take a look at the issue to see if we can figure out what's going wrong.