This merge request contains the updated mingw guidelines text to address
https://pagure.io/packaging-committee/issue/1259
which describes the goal to support MinGW packaging integrated into the native spec files, rather than as completely distinct source packages/components.
The idea of integrated packaging for MinGW + native builds was warmly received when discussed on the mailing lists.
The functional changes to the specfile are also largely un-interesting, as the existing mingw spec file directives could be copied straight into the native package and will do the right thing automatically, producing sub-RPMs for mingw that are indistinguishable from what has historically been produced.
The main notable addition is to suggest that all the mingw related spec directives are placed within conditionals, such that the specfile can be built in derivative distributions (eg CentOS Stream / RHEL) where the Mingw toolchain is not present.
Perhaps the most notable interesting question is how strongly to push towards favouring integrated packaging over separate packaging.
This proposal makes integrated packaging mandatory when the same contributor intends to maintain both native and mingw packages, since that is an maintenance win with little obvious downside. For the case where the mingw support is requested / proposed by someone who is not already the native maintainer, integrated packaging is encouraged, but the native maintainer still has discretion to decline it. It is hoped native package maintainers will be receptive, but we're mindful of not wanting to force them to do something against their will. Similar to the example of how Fedora maintainers are NOT forced to support EPEL branches against their will.
This merge request contains the updated mingw guidelines text to address
https://pagure.io/packaging-committee/issue/1259
which describes the goal to support MinGW packaging integrated into the native spec files, rather than as completely distinct source packages/components.
The idea of integrated packaging for MinGW + native builds was warmly received when discussed on the mailing lists.
The functional changes to the specfile are also largely un-interesting, as the existing mingw spec file directives could be copied straight into the native package and will do the right thing automatically, producing sub-RPMs for mingw that are indistinguishable from what has historically been produced.
The main notable addition is to suggest that all the mingw related spec directives are placed within conditionals, such that the specfile can be built in derivative distributions (eg CentOS Stream / RHEL) where the Mingw toolchain is not present.
Perhaps the most notable interesting question is how strongly to push towards favouring integrated packaging over separate packaging.
This proposal makes integrated packaging mandatory when the same contributor intends to maintain both native and mingw packages, since that is an maintenance win with little obvious downside. For the case where the mingw support is requested / proposed by someone who is not already the native maintainer, integrated packaging is encouraged, but the native maintainer still has discretion to decline it. It is hoped native package maintainers will be receptive, but we're mindful of not wanting to force them to do something against their will. Similar to the example of how Fedora maintainers are NOT forced to support EPEL branches against their will.