unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: 宋文武 <iyzsong@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Help needed with security updates for Qt
Date: Sun, 21 Jun 2015 23:15:03 +0200	[thread overview]
Message-ID: <87r3p4n4q0.fsf@gnu.org> (raw)
In-Reply-To: <87r3p6o4a3.fsf@gmail.com> ("宋文武"'s message of "Sat, 20 Jun 2015 22:14:44 +0800")

宋文武 <iyzsong@gmail.com> skribis:

> Ludovic Courtès <ludo@gnu.org> writes:
>
>> [...]
>>
>>> I'd like to try re-package qt5 with submodules, and drop QtWebEngine.
>>> As same as Debian and NixOS did.
>>
>> And Fedora.  Ricardo found this insightful discussion:
>>
>>   http://lists.qt-project.org/pipermail/development/2015-February/019960.html
>>
>> +1 for removing QtWebEngine and thus have a snippet that removes the
>> bundled Chromium altogether.
> Well, by build with submodule tarballs [1], Qt5 will split into various
> packages:
>   qtbase, qtsvg, qtx11extras, etc.
> The current monolithic qt package will be deprecated.

Ah OK, didn’t know that.

> It seems that some hacks are needed, basically:
>   - when build:
>     Make a 'qt.conf' and union the releated 'lib' and 'mkspecs' for
>     qmake.  Should do in 'qmake-build-system'.
>     FYI: nixpkgs's recipes [2] and qmake reference [3].
>     
>   - when run:
>     Set 'QT_PLUGIN_PATH' and other variables with wrapper and/or
>     profile envs.
>
> And I believe this have to be done if we want to package KDE5,
> since KF5 is a set of plugins for Qt.

Sounds like a good plan.  Thanks for looking into it!

Ludo’.

      reply	other threads:[~2015-06-21 21:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-16 14:20 Help needed with security updates for Qt Mark H Weaver
2015-06-18 12:30 ` Ludovic Courtès
2015-06-19 12:58 ` 宋文武
2015-06-19 13:29   ` Ludovic Courtès
2015-06-20 14:14     ` 宋文武
2015-06-21 21:15       ` Ludovic Courtès [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

  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=87r3p4n4q0.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=iyzsong@gmail.com \
    /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).