guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: %desktop-services now depends on Qt 5, via colord


From: Efraim Flashner
Subject: Re: %desktop-services now depends on Qt 5, via colord
Date: Sat, 14 Jul 2018 22:26:44 +0300
User-agent: Mutt/1.10.0 (2018-05-17)

On Sat, Jul 14, 2018 at 02:00:38PM -0400, Mark H Weaver wrote:
> Hi Tobias,
> 
> address@hidden (Tobias Geerinckx-Rice) writes:
> 
> > nckx pushed a commit to branch master
> > in repository guix.
> >
> > commit 407ef4b38ad394e0b63320b029d95afdd3da6888
> > Author: Tobias Geerinckx-Rice <address@hidden>
> > Date:   Tue Jun 19 20:02:42 2018 +0200
> >
> >     gnu: hplip: Add Qt GUI support.
> >     
> >     Some tools (like ‘hp-toolbox’) still refuse to launch, but at least
> >     others (like ‘hp-systrax’) now seem to work.
> >     
> >     * gnu/packages/cups.scm (hplip)[arguments]: Add #configure-flags for Qt.
> >     [inputs]: Add python-gobject and python-pyqt.
> 
> Until this commit, it was possible to build a desktop system without Qt.
> No longer.
> 
> This commit effectively added most of Qt 5 as a new dependency of
> 'colord' (via 'sane-backends' and 'hplip'), which in turn means that
> _any_ GuixSD system that uses %desktop-services now depends on Qt 5
> libraries, including:
> 
>    qtbase
>    qtconnectivity
>    qtdeclarative
>    qtlocation
>    qtmultimedia
>    qtsensors
>    qtserialport
>    qtsvg
>    qttools
>    qtwebchannel
>    qtwebsockets
>    qtx11extras
>    qtxmlpatterns
> 
> I would greatly prefer to preserve a straightforward way to build a
> desktop system, e.g. a GNOME system, without building Qt 5.
> 
> Thoughts?
> 
>        Mark
> 

It sounds like adding Qt to hplip adds plenty of GUI goodies. Could we
leave hplip as-is and have sane-backends depend on a Qt-less
hplip-minimal or hplip-nogui, since it shouldn't need any GUI from hplip?

-- 
Efraim Flashner   <address@hidden>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]