On Wed, 2 Jul 2025, Jon Turney via Cygwin-apps wrote: > * Ensures that the packaging git repo is updated when the package is. > > * Ensures that the source package is complete; and that the build works and is > repeatable. > > * Ensures that the package is built in a sterile environment. > > * Ensures that the package is serially developed in the git main branch (so > when someone does a NMU, they don't also need to remember to explicitly > communicate any changes made to the maintainer so they don't drop off again in > the next release...) > > * Transparency about, and some degree of auditability on how, the contents of > the install package are generated. >
I would like to suggest that packages be able to be maintained on multiple branches. Cygwin supports having more than one version of a package in the repository, and that may necessitate maintaining multiple versions of a package at once. For example, when I was looking at gcc, I only see 12.4 on main, and 13.4 on playground, but 14 15 and 16 are available to install. Not every package needs this, but the few that do are probably important enough to warrant the complexity.
