Hi,
For a while I have been wondering if it wouldn't be better just to do one ghc Copr per major GHC release rather than one for each minor release... (eg petersen/ghc-8.8 rather than petersen/8.8.1 etc). The argument being that then you will automatically get updated to new minor ghc releases as they come out, and not have to check when a new copr appears and enable it (I suppose I should announce them more widely though I do usually put out an email). I have also been labelling the Fedora module streams by major version: ghc:8.4 (and ghc:8.6 yet to appear).
If you have any opinions on this, please reply to this mail.
Thanks, Jens
ps I probably won't make any change on this until ghc-8.8 is released.
On Sun, Nov 11, 2018 at 07:44:04PM +0900, Jens-Ulrik Petersen wrote:
Hi,
For a while I have been wondering if it wouldn't be better just to do one ghc Copr per major GHC release rather than one for each minor release... (eg petersen/ghc-8.8 rather than petersen/8.8.1 etc). The argument being that then you will automatically get updated to new minor ghc releases as they come out, and not have to check when a new copr appears and enable it (I suppose I should announce them more widely though I do usually put out an email). I have also been labelling the Fedora module streams by major version: ghc:8.4 (and ghc:8.6 yet to appear).
If you have any opinions on this, please reply to this mail.
Yes, I would prefer one copr per major release. I can't see any argument against.
Cheers, Fraser
Thanks, Jens
ps I probably won't make any change on this until ghc-8.8 is released.
haskell@lists.fedoraproject.org
-
Fraser Tweedale -
Jens-Ulrik Petersen