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: [PATCH 02/14] gnu: Add qtimageformats.
Date: Tue, 14 Jun 2016 11:07:03 +0200	[thread overview]
Message-ID: <20160614090703.GA2312@solar> (raw)
In-Reply-To: <20160612202024.GA26270@debian-netbook>

On Sun, Jun 12, 2016 at 11:20:24PM +0300, Efraim Flashner wrote:
> quite possibly the inputs could be shortened, but since they're all
> using qmake for configure I don't really know how to check.

You could compile the packages and use "guix gc --references" to check
which of the inputs are used.

Two basic situations could occur:
- Essentially all inputs of qtbase are also needed for the other packages.
  Then in this special case, I think it does not matter too much to have
  added a few additional inputs, which in any case will have no effect on
  the build result or on installations.
- Only qtbase is used as an input, and the occasional additional one.
  Then I would add the inputs one by one by hand, until the package builds.
I think that the first case is more likely, and would be happy with you
pushing the packages then.

Andreas

  reply	other threads:[~2016-06-14  9:07 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-10 12:10 [PATCH 00/14] modular qt patches Efraim Flashner
2016-06-10 12:10 ` [PATCH 01/14] gnu: Add qtsvg Efraim Flashner
2016-06-10 12:10 ` [PATCH 02/14] gnu: Add qtimageformats Efraim Flashner
2016-06-10 16:30   ` Leo Famulari
2016-06-12 14:12     ` Andreas Enge
2016-06-12 20:20       ` Efraim Flashner
2016-06-14  9:07         ` Andreas Enge [this message]
2016-06-14 10:02           ` Efraim Flashner
2016-06-10 12:10 ` [PATCH 03/14] gnu: Add qtx11extras Efraim Flashner
2016-06-10 12:10 ` [PATCH 04/14] gnu: Add qtxmlpatterns Efraim Flashner
2016-06-10 12:10 ` [PATCH 05/14] gnu: Add qtdeclarative Efraim Flashner
2016-06-10 12:10 ` [PATCH 06/14] gnu: Add qtconnectivity Efraim Flashner
2016-06-10 12:10 ` [PATCH 07/14] gnu: Add qtwebsockets Efraim Flashner
2016-06-10 12:10 ` [PATCH 08/14] gnu: Add qtsensors Efraim Flashner
2016-06-10 12:10 ` [PATCH 09/14] gnu: Add qtmultimedia Efraim Flashner
2016-06-10 12:10 ` [PATCH 10/14] gnu: Add qtwayland Efraim Flashner
2016-06-10 12:10 ` [PATCH 11/14] gnu: Add qtserialport Efraim Flashner
2016-06-10 12:10 ` [PATCH 12/14] gnu: Add qtwebchannel Efraim Flashner
2016-06-10 12:10 ` [PATCH 13/14] gnu: Add qtlocation Efraim Flashner
2016-06-10 16:22   ` Leo Famulari
2016-06-10 12:10 ` [PATCH 14/14] gnu: Add qttools Efraim Flashner
2016-06-12 14:13 ` [PATCH 00/14] modular qt patches Andreas Enge
2016-06-14 10:58   ` Efraim Flashner
2016-06-15 14:16     ` Andreas Enge

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=20160614090703.GA2312@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).