@ObsidianLib That's really impressive! How do you interface with the WinGet catalog? You may be interested in Devolutions/pinget which I develop, and can expose all the *proper* WinGet catalog metadata with search, including from Linux, so you could automate fetching and republishing
2 likes · 21 views
Who else is maintaining a dual-language code base? By this I mean the same application or library written in two languages in parallel, fully, like C# and Rust. What are your strategies to detect drift between the two implementations? Here's an example: Devolutions/pinget
1 like
Who else is maintaining a dual-language code base? By this I mean the same application or library written in two languages in parallel, fully, like C# and Rust. What are your strategies to detect drift between the two implementations? Here's an example: Devolutions/pinget
1 like · 238 views
I added initial support for building those static WinGet repositories in pinget last week, using external makeappx and signtool tools from Windows. It's just a first step, because I'm now making it cross-platform: Devolutions/pinget
1 like · 82 views
Pinget is cross-platform Winget written in both C# and Rust. I know I can make all of this work on a Linux host to publish packages to Windows: Devolutions/pinget
Pinget is cross-platform Winget written in both C# and Rust. I know I can make all of this work on a Linux host to publish packages to Windows: Devolutions/pinget
1 like · 81 views
Mentions
@ObsidianLib That's really impressive! How do you interface with the WinGet catalog? You may be interested in Devolutions/pinget which I develop, and can expose all the *proper* WinGet catalog metadata with search, including from Linux, so you could automate fetching and republishing
Who else is maintaining a dual-language code base? By this I mean the same application or library written in two languages in parallel, fully, like C# and Rust. What are your strategies to detect drift between the two implementations? Here's an example: Devolutions/pinget
Who else is maintaining a dual-language code base? By this I mean the same application or library written in two languages in parallel, fully, like C# and Rust. What are your strategies to detect drift between the two implementations? Here's an example: Devolutions/pinget
I added initial support for building those static WinGet repositories in pinget last week, using external makeappx and signtool tools from Windows. It's just a first step, because I'm now making it cross-platform: Devolutions/pinget
Pinget is cross-platform Winget written in both C# and Rust. I know I can make all of this work on a Linux host to publish packages to Windows: Devolutions/pinget
Pinget is cross-platform Winget written in both C# and Rust. I know I can make all of this work on a Linux host to publish packages to Windows: Devolutions/pinget