From: Eli Zaretskii <eliz@gnu.org>
To: Gavin Smith <gavinsmith0123@gmail.com>
Cc: guix-devel@gnu.org, ludo@gnu.org, bug-texinfo@gnu.org
Subject: Re: Any interest in using HTML for locally-installed Texinfo documentation?
Date: Tue, 09 Apr 2019 09:25:52 +0300 [thread overview]
Message-ID: <83r2ab7kzz.fsf@gnu.org> (raw)
In-Reply-To: <20190408234609.GA9976@darkstar.example.net> (message from Gavin Smith on Tue, 9 Apr 2019 00:46:09 +0100)
> From: Gavin Smith <gavinsmith0123@gmail.com>
> Date: Tue, 9 Apr 2019 00:46:09 +0100
> Cc: guix-devel@gnu.org, Texinfo <bug-texinfo@gnu.org>
>
> I'm still trying to implement very basic functionality in the Qt code.
> I will probably push on with it and see how far I get. If GTK is used
> instead, the needed functionality would be present, and the Qt code
> would be a prototype.
>
> I expect it would be easier to integrate GTK-based code with an automake
> build system (Qt has its own build system tool, qmake). I understand
> from reading various blogs and so forth that GTK has its own problems,
> too. However, it is still plausible that it could be used.
>
> > Also, QtWebEngine relies on bits of Chromium, which is a real challenge
> > from a software freedom viewpoint and from a security viewpoint, to the
> > point that we ended up removing it from our Qt builds in Guix:
> >
> > https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/qt.scm#n143
> > https://lists.gnu.org/archive/html/guix-devel/2015-06/msg00302.html
>
> Those messages don't give a very promising picture.
In case people aren't aware: AFAIK there's also a legal problem with
Qt itself, in that its license is GPLv3, without the "or later"
clause.
next prev parent reply other threads:[~2019-04-09 6:25 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 12:55 Any interest in using HTML for locally-installed Texinfo documentation? Gavin Smith
2019-04-01 14:01 ` sirgazil
2019-04-02 9:37 ` Ludovic Courtès
2019-04-02 15:02 ` Gavin Smith
2019-04-02 16:46 ` Per Bothner
2019-04-07 16:28 ` Gavin Smith
2019-04-08 15:12 ` Ludovic Courtès
2019-04-08 15:39 ` Pierre Neidhardt
2019-04-08 23:46 ` Gavin Smith
2019-04-09 6:25 ` Eli Zaretskii [this message]
2019-04-13 16:21 ` Gavin Smith
2019-04-14 19:25 ` Pronaip
2019-10-15 19:27 ` Gavin Smith
2019-10-15 20:20 ` P
2019-10-15 20:35 ` Gavin Smith
2019-10-15 20:40 ` Per Bothner
2019-10-15 21:00 ` Gavin Smith
2019-10-15 21:09 ` Per Bothner
2019-10-15 21:30 ` Gavin Smith
2019-10-16 1:39 ` Ricardo Wurmus
2019-10-19 20:31 ` Ludovic Courtès
2019-10-22 19:00 ` Gavin Smith
2019-10-22 20:18 ` Gavin Smith
2019-11-03 14:04 ` Ludovic Courtès
2019-11-03 15:37 ` Gavin Smith
2019-11-06 21:49 ` Ludovic Courtès
2019-04-03 21:21 ` Ludovic Courtès
2019-04-04 10:33 ` Gavin Smith
2019-04-02 15:31 ` Per Bothner
2019-04-03 21:11 ` Ludovic Courtès
2019-04-03 22:44 ` Per Bothner
2019-04-04 10:23 ` Gavin Smith
2019-04-04 16:02 ` Ludovic Courtès
2019-04-02 20:12 ` Ricardo Wurmus
2019-04-02 20:27 ` Ricardo Wurmus
2019-04-02 22:58 ` sirgazil
2019-04-02 22:10 ` Per Bothner
2019-04-02 23:09 ` sirgazil
2019-04-03 8:43 ` Gavin Smith
2019-04-03 14:23 ` sirgazil
2019-04-03 14:40 ` Per Bothner
2019-04-03 14:49 ` Ricardo Wurmus
2019-04-02 21:02 ` George Clemmer
2019-04-07 11:08 ` Gavin Smith
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=83r2ab7kzz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bug-texinfo@gnu.org \
--cc=gavinsmith0123@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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 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.