From: Leo Famulari <leo@famulari.name>
To: Thomas Danckaert <post@thomasdanckaert.be>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add qtwebkit.
Date: Sat, 5 Nov 2016 14:45:38 -0400 [thread overview]
Message-ID: <20161105184538.GB11070@jasmine> (raw)
In-Reply-To: <20161102.140509.1673098785705461056.post@thomasdanckaert.be>
On Wed, Nov 02, 2016 at 02:05:09PM +0100, Thomas Danckaert wrote:
> From: Leo Famulari <leo@famulari.name>
> Subject: Re: [PATCH] gnu: Add qtwebkit.
> Date: Sat, 29 Oct 2016 20:22:14 -0400
>
> > Is there any official statement from Qt about these "community
> > releases"? I see that it is hosted on qt.io, so presumably they are
> > somehow blessed by Qt, but I'd like more information.
>
> I wasn't able to find any information at all. Maybe someone on #kde can
> tell us more.
I found this statement on the Qt mailing list:
"QtQuick1 and QtWebKit are _not_ supported anymore since Qt 5.6.
What we have said is that we will provide QtWebKit source packages as
courtesy
on a best-effort basis. That is, also the QtWebKit source package under
http://download.qt.io/community_releases/5.6/5.6.0/
is not part of Qt anymore, and not supported. Use it at your own risk.
There's also no promise we can continue providing these."
source: http://lists.qt-project.org/pipermail/development/2016-May/025923.html
Well, none of this software comes with a warranty, so I think it's fine.
Can you add a code comment mentioning that this package is not
officially supported by the Qt project?
next prev parent reply other threads:[~2016-11-05 18:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-28 9:26 [PATCH] gnu: Add qtwebkit Thomas Danckaert
2016-10-28 14:44 ` Roel Janssen
2016-11-02 12:35 ` Roel Janssen
2016-11-02 13:00 ` Thomas Danckaert
2016-11-02 13:32 ` Roel Janssen
2016-10-30 0:22 ` Leo Famulari
2016-11-02 13:05 ` Thomas Danckaert
2016-11-05 18:45 ` Leo Famulari [this message]
2016-11-05 20:24 ` Thomas Danckaert
2016-11-07 9:17 ` Ludovic Courtès
2016-11-07 9:47 ` Roel Janssen
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=20161105184538.GB11070@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=post@thomasdanckaert.be \
/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).