Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#48990 - [haskell-stack] Package is updated too often
Attached to Project:
Community Packages
Opened by Ruud van Asseldonk (ruudva) - Sunday, 17 April 2016, 09:29 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 17 April 2016, 14:23 GMT
Opened by Ruud van Asseldonk (ruudva) - Sunday, 17 April 2016, 09:29 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 17 April 2016, 14:23 GMT
|
DetailsThis might seem like an odd report, but this package is updated **very** often. It was updated 52 times in the past 100 days, roughly every other day. A few days there even were multiple updates on a single day. This update frequency is something that I would expect of a nightly package, not of a stable product. The stable stack package is updated more often than haskell-stack-git from the AUR (which appears to be unmaintained though) that is supposed to track upstream master. As someone who occasionally builds Haskell projects, I spend more time updating Stack than I spend using it. This costs bandwidth unnecessarily and it pollutes my package cache.
When I look at the tagged releases upstream (https://github.com/commercialhaskell/stack/tags), the amount of releases is modest, 5 in the past 100 days. One package for every upstream release would be fine. Why does Stack need a new package more often? The commit messages suggest that these are all rebuilds with updated dependencies. Surely these are not all security fixes that require immediate action? I would like to request that package updates are limited to one package per upstream release. Of course, if there is a good reason for a rebuild then that is fine. |
This task depends upon
Closed by Doug Newgard (Scimmia)
Sunday, 17 April 2016, 14:23 GMT
Reason for closing: Not a bug
Additional comments about closing: Look up how haskell deals with ABI. The rebuilds are necessary.
Sunday, 17 April 2016, 14:23 GMT
Reason for closing: Not a bug
Additional comments about closing: Look up how haskell deals with ABI. The rebuilds are necessary.