unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: qt: monolithic or modular?
Date: Sun, 5 Jun 2016 11:15:59 +0200	[thread overview]
Message-ID: <20160605091559.GA1504@solar> (raw)
In-Reply-To: <20160605072418.GA10453@debian-netbook>

On Sun, Jun 05, 2016 at 10:24:18AM +0300, Efraim Flashner wrote:
> To be fair, it was only the arm build that took 3.5 hours, i686 and
> x86_64 both took about an hour.

What took 3,5 hours was the "evaluation" on hydra: The time between the
moment I made hydra look at wip-qt, and the moment the first compilation
of a package started, and this at a time where hydra had nothing else
to do. So I do not think it makes sense to continue working in the wip-qt
branch on hydra and to evaluate it ever so often, even more so since so far
nothing depends on it and we will for the time being keep the monolithic
qt-5; you may as well work locally as for other packages.

By the way, dropping the examples made for a factor of 2 in the compilation
time; a nice improvement!

Andreas

  reply	other threads:[~2016-06-05  9:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05  4:22 qt: monolithic or modular? Efraim Flashner
2016-04-05  9:38 ` Ludovic Courtès
2016-04-08  7:10   ` Efraim Flashner
2016-04-09 14:39 ` Andreas Enge
2016-05-18 12:17 ` Efraim Flashner
2016-05-19 12:15   ` Ludovic Courtès
2016-05-19 13:17     ` Efraim Flashner
2016-05-19 15:55       ` Efraim Flashner
2016-05-20 11:59         ` Ludovic Courtès
2016-05-27 19:23           ` Andreas Enge
2016-06-03 20:30             ` Andreas Enge
2016-06-04 15:24               ` Andreas Enge
2016-06-05  7:24               ` Efraim Flashner
2016-06-05  9:15                 ` Andreas Enge [this message]
2016-06-05 10:24                   ` Efraim Flashner
2016-06-05 10:52                     ` Andreas Enge
2016-05-20 11:56       ` Ludovic Courtès

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=20160605091559.GA1504@solar \
    --to=andreas@enge.fr \
    --cc=efraim@flashner.co.il \
    --cc=guix-devel@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).