Re: propagating inputs in ghc-* packages

2016-10-02 Thread Ricardo Wurmus
Eric Bavier writes: > Hello Ricardo, > > On 2016-09-30 04:24, Ricardo Wurmus wrote: >> Hi Guix, >> >> I’m in the middle of upgrading our Haskell packages. (Actually, I’m >> just yak shaving. I need “pandoc-citeproc” for “r-knitr”…) >> >> I noticed that upgrading Haskell packages is a pain in

Re: propagating inputs in ghc-* packages

2016-10-02 Thread Federico Beffa
On Sun, Oct 2, 2016 at 6:21 AM, Ricardo Wurmus wrote: >> That sounds great! Just to be sure: you are saying that if you install >> any library (call it A) and the GHC compiler into your profile then you >> are able to compile your program (making use of library A) without >> also having to manuall

Re: propagating inputs in ghc-* packages

2016-10-02 Thread Ricardo Wurmus
Federico Beffa writes: >>> Ricardo Wurmus writes: >>> Hi Guix, I’m in the middle of upgrading our Haskell packages. (Actually, I’m just yak shaving. I need “pandoc-citeproc” for “r-knitr”…) I noticed that upgrading Haskell packages is a pain in the neck because >

Re: propagating inputs in ghc-* packages

2016-10-01 Thread Leo Famulari
On Sat, Oct 01, 2016 at 09:45:21AM +0200, Ricardo Wurmus wrote: > I’m preparing a patch to remove propagation from all Haskell packages. > Now the question is only whether to do this all in one patch or in one > patch per package… :) I'd say whichever method is easiest :) And then we can test it w

Re: propagating inputs in ghc-* packages

2016-10-01 Thread Federico Beffa
>> Ricardo Wurmus writes: >> >>> Hi Guix, >>> >>> I’m in the middle of upgrading our Haskell packages. (Actually, I’m >>> just yak shaving. I need “pandoc-citeproc” for “r-knitr”…) >>> >>> I noticed that upgrading Haskell packages is a pain in the neck because >>> of propagated inputs. It seems

Re: propagating inputs in ghc-* packages

2016-10-01 Thread Ricardo Wurmus
Federico Beffa writes: > Ricardo Wurmus writes: > >> Hi Guix, >> >> I’m in the middle of upgrading our Haskell packages. (Actually, I’m >> just yak shaving. I need “pandoc-citeproc” for “r-knitr”…) >> >> I noticed that upgrading Haskell packages is a pain in the neck because >> of propagated

propagating inputs in ghc-* packages

2016-09-30 Thread Federico Beffa
Ricardo Wurmus writes: > Hi Guix, > > I’m in the middle of upgrading our Haskell packages. (Actually, I’m > just yak shaving. I need “pandoc-citeproc” for “r-knitr”…) > > I noticed that upgrading Haskell packages is a pain in the neck because > of propagated inputs. It seems that not all packa

Re: propagating inputs in ghc-* packages

2016-09-30 Thread Eric Bavier
Hello Ricardo, On 2016-09-30 04:24, Ricardo Wurmus wrote: Hi Guix, I’m in the middle of upgrading our Haskell packages. (Actually, I’m just yak shaving. I need “pandoc-citeproc” for “r-knitr”…) I noticed that upgrading Haskell packages is a pain in the neck because of propagated inputs. It

propagating inputs in ghc-* packages

2016-09-30 Thread Ricardo Wurmus
Hi Guix, I’m in the middle of upgrading our Haskell packages. (Actually, I’m just yak shaving. I need “pandoc-citeproc” for “r-knitr”…) I noticed that upgrading Haskell packages is a pain in the neck because of propagated inputs. It seems that not all packages have fully declared dependencies