all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: 宋文武 <iyzsong@member.fsf.org>
Cc: guix-devel@gnu.org
Subject: Re: Qt-5 in core-updates
Date: Thu, 17 Mar 2016 22:47:19 +0100	[thread overview]
Message-ID: <20160317214719.GA5598@solar> (raw)
In-Reply-To: <20160202164754.GA9184@debian.eduroam.u-bordeaux.fr>

On Tue, Feb 02, 2016 at 05:47:54PM +0100, Andreas Enge wrote:
> On Mon, Jan 25, 2016 at 09:57:13AM +0800, 宋文武 wrote:
> > This seems like a parallel build issue after I find that,
> > Writing a pyc file is not atomic in python:
> >   <https://bugs.python.org/issue13146>
> > It was fixed in Python 3.3+, but not in Python 2.7.x (the one for
> > building WebKit).
> > I think we can try:
> >  - Patch our python-2.7.x like Ubuntu does.
> >    <https://launchpad.net/ubuntu/+archive/primary/+files/python2.7_2.7.10-4ubuntu1.diff.gz>
> It would be good to revert to parallel builds of qt.
> Actually, there is a version 2.7.11 of python. Should we update first?
> Will this solve our problems?

In fact, there is a very recent release of Qt 5.6, which removes webkit;
so we could try an update. On the other hand, without webkit and the bundled
chromium, there will be no webbrowsers left over... 5.6 is supposed to be
a long term support version, with fixes promised over the next three years.
So would it make sense to reenable chromium (=qtwebengine)?

Andreas

      reply	other threads:[~2016-03-17 21:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-24 19:19 Qt-5 in core-updates Andreas Enge
2016-01-24 23:34 ` Andreas Enge
2016-01-25  1:57 ` 宋文武
2016-01-25  9:25   ` Ludovic Courtès
2016-01-25 18:04   ` Andreas Enge
2016-01-26  2:23     ` 宋文武
2016-01-27 10:38       ` Andreas Enge
2016-02-02 16:47   ` Andreas Enge
2016-03-17 21:47     ` Andreas Enge [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160317214719.GA5598@solar \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=iyzsong@member.fsf.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.