From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: Many perl package failures on core-updates
Date: Thu, 21 Jan 2016 21:48:58 +0100 [thread overview]
Message-ID: <87k2n2y7yd.fsf@gnu.org> (raw)
In-Reply-To: <20160121204209.GC7969@debian> (Andreas Enge's message of "Thu, 21 Jan 2016 21:42:09 +0100")
Andreas Enge <andreas@enge.fr> skribis:
> 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?
Dunno.
> 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?
Could be. OTOH, there’s a risk of Doxygen being effectively “broken by
default” if, as I presume, many programs expect it to be able to
generate PNGs for class diagrams.
I’m chatting, but again, I haven’t actually tried. :-)
Ludo’.
next prev parent reply other threads:[~2016-01-21 20:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-17 16:11 Many perl package failures on core-updates Mark H Weaver
2016-01-17 20:44 ` Ludovic Courtès
2016-01-19 18:41 ` Andreas Enge
2016-01-20 5:07 ` Eric Bavier
2016-01-20 12:27 ` Andreas Enge
2016-01-20 22:15 ` Ludovic Courtès
2016-01-21 20:42 ` Andreas Enge
2016-01-21 20:48 ` Ludovic Courtès [this message]
2016-01-21 21:06 ` Andreas Enge
2016-01-22 17:11 ` Ludovic Courtès
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k2n2y7yd.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).