From: Andreas Enge <andreas@enge.fr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: qt: monolithic or modular?
Date: Fri, 27 May 2016 21:23:13 +0200 [thread overview]
Message-ID: <20160527192313.GA3663@solar> (raw)
In-Reply-To: <87lh35gctz.fsf@gnu.org>
On Fri, May 20, 2016 at 01:59:04PM +0200, Ludovic Courtès wrote:
> Efraim Flashner <efraim@flashner.co.il> skribis:
> > Actually I just checked ./configure --help again, and I can pass the
> > flag '-nomake examples' and it shouldn't make the examples at all. I'm
> > not sure how much compile time it'll save, but it should save us the
> > 25MB of examples that we didn't really want.
> That sounds like a good idea. We could probably create a separate
> ‘qt-examples’ package if someone needs them.
Is that not what our different outputs are for? Concerning the docs, I concur
with Ephraim that we should keep them in the same output, as their size is
negligible. For the examples, passing "-nomake examples" sounds like a good
option to me for now, with a comment in the package; and if someone complains
later, we can add a different output.
Thanks, Ephraim, for working on this!
Andreas
next prev parent reply other threads:[~2016-05-27 19:23 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 [this message]
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
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=20160527192313.GA3663@solar \
--to=andreas@enge.fr \
--cc=guix-devel@gnu.org \
--cc=ludo@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).