From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paul van der Walt <paul@denknerd.org>
Subject: Re: [PATCH] gnu: Add ghc-semigroups.
Date: Thu, 22 Oct 2015 16:15:30 +0200
Message-ID: <87mvvbq9a5.fsf@denknerd.org>
References: <1445483479-19104-1-git-send-email-ericbavier@openmailbox.org>
	<1445503671-30014-1-git-send-email-ericbavier@openmailbox.org>
	<1445503671-30014-15-git-send-email-ericbavier@openmailbox.org>
Content-Type: text/plain
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:41199)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paul@denknerd.org>) id 1ZpGea-0001Rc-Qo
	for guix-devel@gnu.org; Thu, 22 Oct 2015 10:15:41 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <paul@denknerd.org>) id 1ZpGeV-0004dz-O5
	for guix-devel@gnu.org; Thu, 22 Oct 2015 10:15:40 -0400
Received: from mx01.mykolab.com ([95.128.36.1]:13690 helo=mx-out01.mykolab.com)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paul@denknerd.org>) id 1ZpGeV-0004dh-EG
	for guix-devel@gnu.org; Thu, 22 Oct 2015 10:15:35 -0400
In-reply-to: <1445503671-30014-15-git-send-email-ericbavier@openmailbox.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: ericbavier@openmailbox.org
Cc: guix-devel@gnu.org


On 2015-10-22 at 10:47, quoth ericbavier@openmailbox.org:
>> +    (inputs
>> +     `(("ghc-text" ,ghc-text)
>> +       ("ghc-hashable" ,ghc-hashable)))
>
> Do these not need to also be propagated?

This is a comment that comes up frequently.  To be honest, i don't know
how to check.  My packaging strategy has been,

1) put everything in `inputs`

2) make sure the package P1 builds

3) use P1 as an input elsewhere, say in P2

4) if and only if P2 cannot build because of the usual "broken package,
   missing dependencies for P1" error, i add the missing packages to
   `propagated-inputs` of P1.

So no, pragmatically speaking, those inputs do not need to be
propagated, because subsequent builds work fine (up to and including
Idris, which was the root of the dependency tree causing me to add this
and many other packages).

If, however, you believe it's preferable to put the inputs you mention
into `propagated-inputs`, i will not provide any resistance.

Regards,
p.