Main changes:
I can provide a more detailed changelog and comments if needed, but most of the remaining changes are just minor tweaks and small updates.
I have one question about the use of BuildRequires: ghc-*-static, when it is provided by ghc-*-devel: is it mandatory? I ask because eg we have a source package ghc-yesod-static for example which creates resolver ambiguity with the ghc-yesod-static provided by ghc-yesod-devel.
BuildRequires: ghc-*-static
ghc-*-devel
ghc-yesod-static
ghc-yesod-devel
Naively the solution could be to provide and require ghc-*-static%{_isa} instead. But of course this is not allowed for BuildRequires, therefore I prefer to use BuildRequires: ghc-*-devel at least where there is ambiguity.
ghc-*-static%{_isa}
BuildRequires: ghc-*-devel
rebased onto 5e9d0bb7a8a21618d92f8b2fed7978483f6c77b4
I suggest you help the resolver via:
BuildRequires: (ghc-yesod-static with ghc-yesod-devel)
Meaning a single package needs to provide both.
However, would it make snese to avoid the name clash in the first place?
Update of the Haskell Packaging Guidelines (+1:5, 0:0, -1:0)
Pull-Request has been merged by churchyard
Thank you, appreciate the review and the helpful comments about the corner case static provides conflict.
Main changes:
I can provide a more detailed changelog and comments if needed, but most of the remaining changes are just minor tweaks and small updates.