From mboxrd@z Thu Jan  1 00:00:00 1970
From: Andreas Enge <andreas@enge.fr>
Subject: Re: Many perl package failures on core-updates
Date: Thu, 21 Jan 2016 21:42:09 +0100
Message-ID: <20160121204209.GC7969@debian>
References: <87lh7op4nd.fsf@netris.org> <87y4bo3phm.fsf@gnu.org>
	<20160119184112.GA15036@debian>
	<20160120122707.GA16730@debian.eduroam.u-bordeaux.fr>
	<87mvrzx5hz.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:49934)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andreas@enge.fr>) id 1aMM3e-0002as-MZ
	for guix-devel@gnu.org; Thu, 21 Jan 2016 15:42:19 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <andreas@enge.fr>) id 1aMM3c-0001ef-F7
	for guix-devel@gnu.org; Thu, 21 Jan 2016 15:42:18 -0500
Received: from mailrelay6.public.one.com ([91.198.169.200]:19542)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <andreas@enge.fr>) id 1aMM3c-0001eR-4N
	for guix-devel@gnu.org; Thu, 21 Jan 2016 15:42:16 -0500
Content-Disposition: inline
In-Reply-To: <87mvrzx5hz.fsf@gnu.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: Ludovic =?iso-8859-15?Q?Court=E8s?= <ludo@gnu.org>
Cc: guix-devel@gnu.org

On Wed, Jan 20, 2016 at 11:15:04PM +0100, Ludovic Courtès wrote:
> I guess Graphviz was propagated so that ‘doxygen’ can produce class
> diagrams out-of-the-box (it probably looks for ‘dot’ in $PATH.)  So I
> would probably keep it propagated.

I do not remember anymore, although it was me to do it (well, in April 2014).
At some point in time doxygen depended on graphviz, then the dependency
was dropped according to the changelog on the web site. But this was before
I added it, so you may be right. Does it have any impact on packages
that depend on doxygen?

I wonder if this is not a case where we should leave it to the user to
install or not the additional program, since doxygen should still be
functional without this feature?

Andreas