all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric Bavier <ericbavier@openmailbox.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>,
	Guix-devel
	<guix-devel-bounces+ericbavier=openmailbox.org@gnu.org>
Subject: Re: propagating inputs in ghc-* packages
Date: Fri, 30 Sep 2016 09:37:15 -0500	[thread overview]
Message-ID: <721e3b2f0b9accb7f7efc59722baa77e@openmailbox.org> (raw)
In-Reply-To: <87oa35spxl.fsf@elephly.net>

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 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?

Commit e17d513381296b (from almost a year ago!) was intended to allow us 
to remove propagated inputs from our ghc-* packages.  But I didn't 
follow-up at the time, for reasons I forget now, in actually 
un-propagating those inputs.  So if you want to try to do that, it might 
just work.

-- 
`~Eric

  reply	other threads:[~2016-09-30 14:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-30  9:24 propagating inputs in ghc-* packages Ricardo Wurmus
2016-09-30 14:37 ` Eric Bavier [this message]
2016-10-02 11:59   ` Ricardo Wurmus
  -- strict thread matches above, loose matches on Subject: below --
2016-09-30 21:07 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

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=721e3b2f0b9accb7f7efc59722baa77e@openmailbox.org \
    --to=ericbavier@openmailbox.org \
    --cc=guix-devel-bounces+ericbavier=openmailbox.org@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.