unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ng0@we.make.ritual.n0.is>
To: Roel Janssen <roel@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Where is qtwebkit?
Date: Thu, 13 Oct 2016 19:18:25 +0000	[thread overview]
Message-ID: <87lgxsoy66.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87bmyo2weg.fsf@gnu.org>

Roel Janssen <roel@gnu.org> writes:

> ng0 writes:
>
>> I am currently packaging supercollider, and it would be nice to have
>> qtwebkit... but I can't find it for Guix. How do I use it in a packaging
>> defition? Do we have it at all? Is someone working on it? I've read a
>> thread where someone pointed out it was moved but that was of no help
>> either.
>>
>> * Qt >= 5.3 (+ qtwebkit)
>>    * http://qt-project.org
>>    * cross-platform graphical user interface library, for Qt IDE and sclang's Qt GUI kit
>
> I think QtWebkit has been removed from Qt in favor of the QtWebEngine
> (based on Chromium?).

Like I was told in IRC freenode. I wonder if supercollider really needs
qt4 instead of qt5 or if qtwebkit is the MIT-license of the webkits:
they say qtwebkit, but what they really mean is qtwebengine.
I'll ask on their mailinglist.

> From https://blog.qt.io/blog/2016/03/16/qt-5-6-released/:
>> With 5.6, Qt WebKit and Qt Quick 1 will no longer be supported and are
>> dropped from the release. The source code for these modules will still
>> be available. You can continue to compile and use these modules, but
>> we will not be supporting them any longer.
>
> So it should still be possible to compile the source code.  I downloaded
> the source code and tried to compile it but I couldn't find any 'find
> . -name "*webkit*"' at all!
>
> Kind regards,
> Roel Janssen
>

Thanks for the reply

      reply	other threads:[~2016-10-13 19:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-12 11:55 Where is qtwebkit? ng0
2016-10-13 13:47 ` Roel Janssen
2016-10-13 19:18   ` ng0 [this message]

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=87lgxsoy66.fsf@we.make.ritual.n0.is \
    --to=ng0@we.make.ritual.n0.is \
    --cc=guix-devel@gnu.org \
    --cc=roel@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).