On Wed, Mar 01, 2023 at 01:45:11PM +0000, Daniel P. Berrangé wrote: > Our goal is to strongly encourage the use of integrated mingw packaging, > but still allow native package maintainers the discretion to opt-out of > this if they feel strongly against handling mingw themselves. The keys > terms of the updated guidelines are this paragraph: > > [quote] > * Where the same Fedora contributors intend to maintain both the native > and MinGW builds of a package, they **MUST** use the integrated packaging > approach. > > * Where the upstream project supports the Windows platform as an official > build target and has automated CI, contributors **SHOULD** prefer the > integrated MinGW packaging approach. While native package maintainers are > encouraged to accept this, they may decline this suggestion at their > discretion. When I first read this, it seemed like it was saying that if the upstream project supports Windows we (strongly) should produce a mingw package. I understand this is not what you're saying, but perhaps it could be clarified by adding "... and the Fedora packager wishes to provide a mingw library" > * Where the upstream project does not have automated testing of Windows > builds, the MinGW package support **MAY** use the integrated packaging > approach, subject to agreement of the native package maintainer. > > * Where the upstream project only supports Windows builds, the separate > packaging approach **MUST** be used. There will be no corresponding > native package in Fedora expected. This situation is rare. I'm actually trying to think of a case. Maybe the tools I wrote like mingw-nsiswrapper and mingw-crossreport? The second one should probably be removed, since it's not very relevant today. > * When a contributor proposes a new native package to Fedora that provides > libraries that are known to support Windows, the reviewer **SHOULD** > inquire whether the contributor would like to add MinGW builds at the > same time. The contributor **MAY** decline this suggestion at their > discretion. > [/quote] Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://people.redhat.com/~rjones/virt-top _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
