From mboxrd@z Thu Jan 1 00:00:00 1970 From: Federico Beffa Subject: Re: propagating inputs in ghc-* packages Date: Sat, 1 Oct 2016 11:14:11 +0200 Message-ID: References: <871t00v7fy.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38757) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bqGN3-00024n-Un for guix-devel@gnu.org; Sat, 01 Oct 2016 05:14:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bqGN2-0000fp-QF for guix-devel@gnu.org; Sat, 01 Oct 2016 05:14:13 -0400 Received: from mail-vk0-x22c.google.com ([2607:f8b0:400c:c05::22c]:35030) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bqGN2-0000fc-MC for guix-devel@gnu.org; Sat, 01 Oct 2016 05:14:12 -0400 Received: by mail-vk0-x22c.google.com with SMTP id 192so123584480vkl.2 for ; Sat, 01 Oct 2016 02:14:12 -0700 (PDT) In-Reply-To: <871t00v7fy.fsf@elephly.net> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Ricardo Wurmus Cc: Guix-devel >> Ricardo Wurmus writes: >> >>> Hi Guix, >>> >>> I=E2=80=99m in the middle of upgrading our Haskell packages. (Actually= , I=E2=80=99m >>> just yak shaving. I need =E2=80=9Cpandoc-citeproc=E2=80=9D for =E2=80= =9Cr-knitr=E2=80=9D=E2=80=A6) >>> >>> 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 and just work accidentally because of propagated >>> inputs of a related package. This also makes upgrades more difficult >>> because I can get substitutes from Hydra that depend on older versions >>> of some Haskell packages. >>> >>> It looks like Haskell binaries actually embed references to other >>> Haskell packages, so I=E2=80=99m not sure we actually need to propagate= anything >>> at all. Could someone please confirm this? >> >> From what I recall, binary executables include references to packages, >> but libraries do not. So, at least at the time I wrote the first >> version of the haskell-build-system, propagated inputs seemed to be >> necessary for packages providing libraries, but not for ones providing >> applications. > > Thanks for this comment. With Eric Bavier=E2=80=99s patch this seems no = longer > necessary. I=E2=80=99ve already rebuilt a lot of Haskell packages withou= t any > propagation (and some added inputs), and I=E2=80=99ve got working librari= es and > executables. I=E2=80=99m still rebuilding remaining Haskell packages but= I=E2=80=99m > now convinced that propagation is no longer needed with the current > version of the build system. > > I=E2=80=99m preparing a patch to remove propagation from all Haskell pack= ages. > Now the question is only whether to do this all in one patch or in one > patch per package=E2=80=A6 :) 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 manually install any input of library A? Regards, Fede