Packaging and Redistribution

What you may redistribute, what you may not, and where third party packages stand.

Warning

This page is for people who want to redistribute Wintty to others. If you just want to use it, start at Install.

The source

The source is MIT licensed, and the licence says what you may do with it. You can build it, modify it, and redistribute your build. You do not need permission and you do not need to ask.

If you do redistribute a build, please make it obvious that it is yours rather than an official one, so that a problem in your build does not arrive here as a bug report. Naming it something other than Wintty is the simplest way.

The signed builds

The published builds are a different matter. They are signed by Ship Digital Ltd, and that signature is a statement about who produced the file. Redistributing them detaches that statement from the process that makes it meaningful, so please do not mirror or repackage them.

They are also served only to authorized accounts, which is what the paid tiers pay for. Passing them on undercuts the thing that funds the work.

Package managers

Wintty is not on winget or Chocolatey, and is not planning to be.

Both of those repositories need an installer that anyone can download without signing in, so their tooling can fetch it, verify its hash and confirm it installs. Every published Wintty build is gated behind a sponsorship, so there is nothing for such a listing to point at. This is a constraint of how those repositories work rather than a lack of interest.

If you want Wintty on a package manager inside your own organisation, that is a different question and a solvable one. See Pro Enterprise.

If you are considering maintaining a package anyway, please open an issue on the repository first so we can work out how it interacts with the signed builds and the update channels.