[Package Request]: TrID

[smsimeonov]

How can we help?

I would like someone else to build the manifest.

Please read and ensure the following

• The installer meets the above requirements

Please provide the following information

Download Page Url: https://mark0.net/soft-trid-e.html
Publisher: Marco Pontello
Package Name: TrID
Description: TrID is a useful cli utility that helps you identify what file you are dealing with, regardless of the file extension or lack thereof
Package Version: 2.24
Installer URL: https://mark0.net/download/trid_w32.zip

NOTE: For the package to be useful, the TrID definitions also need to be loaded with the TrID portable executable from the Installer ZIP. This URL for the definitions is: https://mark0.net/download/triddefs.zip
They only need to be in the same folder as the executable for them to work

[Dragon1573]

Note

For the package to be useful, the TrID definitions also need to be loaded with the TrID portable executable from the installer ZIP archive. They only need to be in the same folder as the executable for them to work.

winget.exe does not support these kinds of packages. Although winget.exe currently support Dependencies feature, but they'll be regarded as separate packages and install to different folders. They can't "be in the same folder as the executable".

If the executable and definitions can be packaged into a single install wizard with any well-known install technology (prefer WiX, Burn, InnoSetup, Nullsoft, MSI), it would be great.

[smsimeonov]

I created a Github repository with Actions to pull those two zips, join them and release as a single zip.
If we could, we can use that as a source. I know winget can deploy .zip packaged software.
https://github.com/smsimeonov/TrID-Bundled

[Dragon1573]

I created a Github repository with Actions to pull those two zips, join them and release as a single zip.

Wow! That's really convenient. ❤️

If we could, we can use that as a source. I know winget can deploy .zip packaged software.

But winget-pkgs team mostly not accept third-party (such as we packaged them two into a single file) installers.

Maybe we should create PRs to the publisher for enabling features of installer wizard?