From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eli Zaretskii Subject: Re: Any interest in using HTML for locally-installed Texinfo documentation? Date: Tue, 09 Apr 2019 09:25:52 +0300 Message-ID: <83r2ab7kzz.fsf@gnu.org> References: <87a7h8u4r4.fsf@gnu.org> <20190402150245.GA30067@darkstar> <256d60e8-0148-1dd3-4c9d-86e14b42060b@bothner.com> <20190407162804.GA28500@darkstar.example.net> <87k1g4v8dq.fsf@gnu.org> <20190408234609.GA9976@darkstar.example.net> Return-path: In-reply-to: <20190408234609.GA9976@darkstar.example.net> (message from Gavin Smith on Tue, 9 Apr 2019 00:46:09 +0100) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-texinfo-bounces+gnu-bug-texinfo2=m.gmane.org@gnu.org Sender: "bug-texinfo" To: Gavin Smith Cc: guix-devel@gnu.org, ludo@gnu.org, bug-texinfo@gnu.org List-Id: guix-devel.gnu.org > From: Gavin Smith > Date: Tue, 9 Apr 2019 00:46:09 +0100 > Cc: guix-devel@gnu.org, Texinfo > > 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.