From: Efraim Flashner <efraim@flashner.co.il>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 02/14] gnu: Add qtimageformats.
Date: Sun, 12 Jun 2016 23:20:24 +0300 [thread overview]
Message-ID: <20160612202024.GA26270@debian-netbook> (raw)
In-Reply-To: <20160612141221.GA20207@solar>
[-- Attachment #1: Type: text/plain, Size: 2126 bytes --]
On Sun, Jun 12, 2016 at 04:12:21PM +0200, Andreas Enge wrote:
> On Fri, Jun 10, 2016 at 12:30:45PM -0400, Leo Famulari wrote:
> > On Fri, Jun 10, 2016 at 03:10:13PM +0300, Efraim Flashner wrote:
> > > +(define-public qtimageformats
> > > + (package (inherit qtsvg)
> > These patches make me realize my understanding of package inheritance is
> > unclear.
> >
> > If qtsvg is updated, but no other changes are made, will qtimageformats
> > (and all the other packages that inherit from qtsvg) need to be rebuilt
> > as well?
> >
> > Looking at `guix refresh -l` and `guix gc --references` suggests the
> > answer is "no".
>
> My understanding is that not the package definition, but the derivation
> counts. So for instance, if the version is increased in qtsvg, this new
> version also appears in qtimageformats, but if it is set back there, not
> even the package definition has changed.
>
> So this should be safe; in a sense, the inheritance from qtsvg creates a
> "qt build system"; since this is so far only used internally to build qt
> itself, I think it is okay to not expose it to the exterior world.
>
> However, another question: Are all the inputs for qtbase needed for all the
> other modules, too, or could the list be trimmed?
>
> Andreas
>
quite possibly the inputs could be shortened, but since they're all
using qmake for configure I don't really know how to check. The best I
have for cross-distro comparison is debian:
$ apt-cache depends libqt5svg5
libqt5svg5
PreDepends: dpkg
dpkg:i386
Depends: libc6
Depends: libqt5core5a
Depends: libqt5gui5
Depends: libqt5widgets5
Depends: libstdc++6
Depends: <qtbase-abi-5-5-1>
Depends: zlib1g
I don't think I've seen anything like <qtbase-abi-5-5-1> before, but I'm
assuming its the list of inputs/depends that qtbase-5.5.1 uses in
Debian. qtcore, qtgui and qtwidgets are all outputs of qtbase.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-06-12 20:20 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 [this message]
2016-06-14 9:07 ` Andreas Enge
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=20160612202024.GA26270@debian-netbook \
--to=efraim@flashner.co.il \
--cc=andreas@enge.fr \
--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).