From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Nils Gillmann <ng0@n0.is>
Cc: guix-devel@gnu.org
Subject: Re: hplip qt
Date: Thu, 21 Jun 2018 23:53:25 +0200 [thread overview]
Message-ID: <87602bbycq.fsf@lapdog.tobias.gr> (raw)
In-Reply-To: <20180621211332.7cbzlagcmbypygj3@abyayala>
Hullo ng0,
Nils Gillmann wrote:
> Tobias Geerinckx-Rice <me@tobias.gr> added in
> 407ef4b38ad394e0b63320b029d95afdd3da6888
> support for Qt to Hplip. What feels like a lifetime ago, my
> patch with the same
> intention was reviewed and to be worked in a separation of Qt
> and hplip, which
> I found reasonable at that time but drowned in all the branches
> I had back then.
Where was this?
> I still find Qt as a dependency for hplip unreasonable.
One possible problem is that our PyQt doesn't benefit from the
modularity (FWIW) of our Qt packages. I doubt HP's widgets need
qtmultimedia, qtwebchannel, or qtlocation, but there they are
anyway, probably wasting a few hundred MiB in total.
> Can we split the package up as we did for Octave?
If you can separate the GUI tools from the driver without breaking
anything — including user expectations — go for it! Any idea how
other distributions handle this?
I agree that a separate UI output (ideally) or package would be
nicer than the monolith we have now, but I don't find an unusable
UI to be in any way more ‘reasonable’ than adding the right
dependency to fix it.
Kind regards,
T G-R
prev parent reply other threads:[~2018-06-21 21:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 21:13 hplip qt Nils Gillmann
2018-06-21 21:53 ` Tobias Geerinckx-Rice [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=87602bbycq.fsf@lapdog.tobias.gr \
--to=me@tobias.gr \
--cc=guix-devel@gnu.org \
--cc=ng0@n0.is \
/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).