On Mon, 2016-07-25 at 18:06 +0200, Johannes Löthberg wrote:
What about the packages provided by ghc? Guess you could do something similar to get the provides list from pacman, hmm.. Thanks though!
GHC only updates once every 4-5 months and provides few packages, so I don't mind handling those manually.
On 26/07, Nicola Squartini via aur-general wrote:
On Mon, 2016-07-25 at 18:06 +0200, Johannes Löthberg wrote:
What about the packages provided by ghc? Guess you could do something similar to get the provides list from pacman, hmm.. Thanks though!
GHC only updates once every 4-5 months and provides few packages, so I don't mind handling those manually.
True. I made my own script[0] handle that anyway though! Your script was really useful to start on mine though, so thanks. :)
[0]: https://gist.github.com/kyrias/5cd320ce6ced969f35f5dd133c5519c4
Nicola Squartini via aur-general aur-general@archlinux.org writes:
On Mon, 2016-07-25 at 18:06 +0200, Johannes Löthberg wrote:
What about the packages provided by ghc?Guess you could do something similar to get the provides list from pacman, hmm..Thanks though!
GHC only updates once every 4-5 months and provides few packages, so I don't mind handling those manually.
There are some (old, and not often used) scripts in the archhaskell repo[1] that may serve as a starting point for upgrades of ghc. Personally I tend to
1. build the new ghc 2. install and check the packages and versions 3. adjust the PKGBUILD 4. re-build (using the new ghc)
(I like the idea of having a package of ghc that's built using the same version of ghc :)
/M
[1]: https://github.com/archhaskell/habs/tree/master/ghc/helpers
aur-general@lists.archlinux.org