From: Leo Famulari <leo@famulari.name>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: texmaker, Qt and Chromium
Date: Sat, 8 Oct 2016 18:09:39 -0400 [thread overview]
Message-ID: <20161008220939.GB27027@jasmine> (raw)
In-Reply-To: <8737k7urk0.fsf@elephly.net>
On Sat, Oct 08, 2016 at 11:18:55AM +0200, Ricardo Wurmus wrote:
>
> Roel Janssen <roel@gnu.org> writes:
> > Also, I know that Calibre is broken (it compiles file, but it doesn't
> > start anymore) since we are missing the QtWebKit module.
>
> Yet another package for which we would need to decide: remove the
> package or add “qtwebengine”.
I don't know anything about qtwebengine besides what's in this
discussion but, based on that, I think we should package qtwebengine if
Calibre requires it.
As far as I know, there is no program that can replace Calibre's ebook
conversion and formatting tools.
next prev parent reply other threads:[~2016-10-09 6:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 19:17 texmaker, Qt and Chromium Ricardo Wurmus
2016-10-08 8:14 ` Roel Janssen
2016-10-08 9:18 ` Ricardo Wurmus
2016-10-08 9:35 ` David Craven
2016-10-08 9:45 ` Ricardo Wurmus
2016-10-08 9:50 ` David Craven
2016-10-08 22:09 ` Leo Famulari [this message]
2016-10-08 8:21 ` John Darrington
2016-10-08 8:55 ` Danny Milosavljevic
2016-10-08 9:16 ` Ricardo Wurmus
2016-10-08 9:55 ` Danny Milosavljevic
2016-10-09 20:13 ` Security updates (was Re: texmaker, Qt and Chromium) Leo Famulari
2016-10-09 21:07 ` Kei Kebreau
2016-10-09 22:09 ` Leo Famulari
2016-10-09 21:33 ` Ludovic Courtès
2016-10-11 11:40 ` ng0
2016-10-08 9:12 ` texmaker, Qt and Chromium David Craven
2016-10-08 9:23 ` Ricardo Wurmus
2016-10-08 21:35 ` Roel Janssen
2016-10-08 21:46 ` Ricardo Wurmus
2016-10-10 10:41 ` Roel Janssen
2016-10-08 21:53 ` Danny Milosavljevic
2016-10-08 20:18 ` Efraim Flashner
2016-10-08 21:00 ` Ricardo Wurmus
2016-10-08 21:08 ` Efraim Flashner
2016-10-08 21:20 ` ng0
2016-10-08 21:24 ` Danny Milosavljevic
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=20161008220939.GB27027@jasmine \
--to=leo@famulari.name \
--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.