From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Subject: Re: 01/01: gnu: cups-filters: Update to 1.11.5.
Date: Sun, 15 Jan 2017 14:06:19 -0500 [thread overview]
Message-ID: <20170115190619.GB29718@jasmine> (raw)
In-Reply-To: <20161029230842.0AC4822011A@vcs.savannah.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
On Sat, Oct 29, 2016 at 11:08:42PM +0000, Tobias Geerinckx-Rice wrote:
Hi Tobias!
> nckx pushed a commit to branch core-updates
> in repository guix.
>
> commit 4ab016e0ab9bfff2f108d1fc6f0ed3b0e1eff735
> Author: Tobias Geerinckx-Rice <me@tobias.gr>
> Date: Sun Oct 30 00:07:08 2016 +0200
>
> gnu: cups-filters: Update to 1.11.5.
>
> * gnu/packages/cups.scm (cups-filters): Update to 1.11.5.
> [arguments]: Add ‘--with-gs-path=’ to #:configure-flags.
> [inputs]: Add mupdf.
I wonder, do you have a use for the "mutool" integration that this
enabled, or did you add it simply because the configure phase fails
without it?
If the latter, I think we should instead pass '--disable-mutool', so
that cups-filters doesn't depend on two different PDF libraries.
Otherwise, we should make cups-filters refer directly to mupdf's mutool,
instead of looking for it on PATH.
Your thoughts?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next parent reply other threads:[~2017-01-15 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161029230841.27311.65622@vcs.savannah.gnu.org>
[not found] ` <20161029230842.0AC4822011A@vcs.savannah.gnu.org>
2017-01-15 19:06 ` Leo Famulari [this message]
2017-01-16 15:25 ` 01/01: gnu: cups-filters: Update to 1.11.5 Tobias Geerinckx-Rice
2017-01-16 20:25 ` 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
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=20170115190619.GB29718@jasmine \
--to=leo@famulari.name \
--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).