unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Staying on top of Qt security
Date: Sat, 20 Feb 2016 22:46:49 +0200	[thread overview]
Message-ID: <20160220224649.48c3fd10@debian-netbook> (raw)
In-Reply-To: <20160218223529.GC9390@jasmine>

[-- Attachment #1: Type: text/plain, Size: 2339 bytes --]

On Thu, 18 Feb 2016 17:35:29 -0500
Leo Famulari <leo@famulari.name> wrote:

> On Thu, Feb 18, 2016 at 09:43:49PM +0100, Andreas Enge wrote:
>  [...]  
>  [...]  
>  [...]  
> > > $ guix refresh -l qt-4                        
> > > Building the following 18 packages would ensure 24 dependent packages
> > > are rebuilt: soprano-2.9.4 python2-pyqt-4.11.4 polkit-qt-1-0.112.0
> > > frescobaldi-2.18.1 keepassx-2.0.2 hydrogen-0.9.5.1 strigi-0.7.8
> > > attica-0.4.2 pumpa-0.9.2 libdbusmenu-qt-0.9.2 phonon-4.8.3
> > > brdf-explorer-17 gpsbabel-1.5.0 librecad-2.0.6-rc
> > > alsa-modular-synth-2.1.2 qtractor-0.7.3 ardour-4.4 jalv-1.4.6  
> > 
> > Some of them have no dependent packages, and I think they are mainly or
> > exclusively used for KDE-4, which I started packaging a while ago (and
> > dropped again when I got my Novena, as it turns out that KDE is too
> > resource demanding). In any case, we would package KDE-5 now, and I would
> > suggest to simply remove these packages. There are traces in git, so if
> > it turns out we will need them in the end, we can still revive them.
> > This concerns:
> > attica soprano strigi polkit-qt automoc4 qjson libdbusmenu-qt
> > So while we are it it, I suggest to simply remove kde.scm (there is no use
> > in keeping a lonely oxygen-icons around...).
> > 
> > Also, python2-pyqt has no dependent package.
> > 
> > I looked at frescobaldi; they claim that a Qt-5 port is on the TODO list
> > for their version 3, but without giving any timings.
> > 
> > If there is no outcry, I will remove the above-mentioned packages/modules.
> > 
> > Could maybe people using the other packages have a look at them?  
> 
> I noticed that Efraim has upgraded a few qt-4 dependencies so that they
> can use qt(-5).
> 

A bunch of the programs that use qt-4 currently use the cmake-build-system,
and it seems that cmake or something else reads Qt > 4.2 and won't accept
qt-5 as an input. Currently CMake is at 3.3.2, I was going to update it to
3.4.3 but 3.5.0 is almost out. It could be that this is what allows those
programs to be switched.


-- 
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: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-02-20 20:47 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-14 20:01 Staying on top of Qt security Leo Famulari
2016-02-18 20:43 ` Andreas Enge
2016-02-18 22:35   ` Leo Famulari
2016-02-20 20:46     ` Efraim Flashner [this message]
2016-02-18 22:53   ` Christopher Allan Webber
2016-02-18 22:59     ` Andreas Enge
2016-02-20 18:27       ` Christopher Allan Webber
2016-02-21  7:28         ` Leo Famulari
2016-02-21 17:42           ` Christopher Allan Webber
2016-02-21 19:27             ` Leo Famulari
2016-02-22 19:53             ` Andreas Enge
2016-02-22 20:19               ` Leo Famulari
2016-02-22 20:40           ` Andreas Enge
2016-02-22 20:36   ` Andreas Enge
2016-02-25  8:35 ` Andreas Enge
2016-02-25  9:04   ` Andreas Enge
2016-02-25  9:06     ` Andreas Enge
2016-02-25  9:36       ` Ricardo Wurmus
2016-03-05 11:41       ` Andreas Enge
2016-03-05 21:16         ` Ricardo Wurmus
2016-03-05 21:18           ` Andreas Enge
2016-03-09  8:46             ` Ricardo Wurmus
2016-02-25  9:38   ` Ricardo Wurmus
2016-02-25 20:22     ` 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=20160220224649.48c3fd10@debian-netbook \
    --to=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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).