all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
* propagating inputs in ghc-* packages
@ 2016-09-30 21:07 Federico Beffa
  2016-10-01  7:45 ` Ricardo Wurmus
  0 siblings, 1 reply; 9+ messages in thread
From: Federico Beffa @ 2016-09-30 21:07 UTC (permalink / raw)
  To: rekado; +Cc: Guix-devel

Ricardo Wurmus <rekado@elephly.net> 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 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’m 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.

Regards,
Fede

^ permalink raw reply	[flat|nested] 9+ messages in thread
* propagating inputs in ghc-* packages
@ 2016-09-30  9:24 Ricardo Wurmus
  2016-09-30 14:37 ` Eric Bavier
  0 siblings, 1 reply; 9+ messages in thread
From: Ricardo Wurmus @ 2016-09-30  9:24 UTC (permalink / raw)
  To: guix-devel

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 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’m not sure we actually need to propagate anything
at all.  Could someone please confirm this?

~~ Ricardo

^ permalink raw reply	[flat|nested] 9+ messages in thread

end of thread, other threads:[~2016-10-02 16:13 UTC | newest]

Thread overview: 9+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-09-30 21:07 propagating inputs in ghc-* packages Federico Beffa
2016-10-01  7:45 ` Ricardo Wurmus
2016-10-01  9:14   ` Federico Beffa
2016-10-02  4:21     ` Ricardo Wurmus
2016-10-02 15:42       ` Federico Beffa
2016-10-01 16:31   ` Leo Famulari
  -- strict thread matches above, loose matches on Subject: below --
2016-09-30  9:24 Ricardo Wurmus
2016-09-30 14:37 ` Eric Bavier
2016-10-02 11:59   ` Ricardo Wurmus

Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.