all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: 37908@debbugs.gnu.org
Subject: [bug#37908] [PATCH 0/2] Remove monolithic qt5 (and other unused package)
Date: Fri, 25 Oct 2019 13:43:00 +0300	[thread overview]
Message-ID: <20191025104300.GK15460@E5400> (raw)
In-Reply-To: <20191025103449.GI15460@E5400>

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

On Fri, Oct 25, 2019 at 01:34:49PM +0300, Efraim Flashner wrote:
> On Thu, Oct 24, 2019 at 09:20:56PM +0200, Hartmut Goebel wrote:
> > The monolithic `qt` package was only used as a base to inhert `qt-4` from.
> > 
> > For testing this change does not change qt-4 in any way:
> > - run ./pre-inst-env guix build qt@4.8.7
> > - apply patch
> > - again run ./pre-inst-env guix build qt@4.8.7
> > 
> > -> qt@4.8.7 will *not* be build again. To avoid any rebuilds, I even refrined
> > from sorting the inputs. :-)
> > 
> > The other patch removes a package which has been merged into qtdeclarative as
> > of Qt 5.8.0 and is not used anywhere.
> > 
> > 
> > Hartmut Goebel (2):
> >   gnu: Remove qtdeclarative-render2d.
> >   gnu: Remove monolithic qt5.
> > 
> >  gnu/packages/qt.scm | 328 +++++++-------------------------------------
> >  1 file changed, 49 insertions(+), 279 deletions(-)
> > 
> 
> On qtdeclarative-render2d, I think the only reason to possibly keep it
> is Debian old-stable (or old-old stable, not sure) packaged the 5.7
> series, but I don't think they even used it for anything.
> 
> Very much vote yes on monolithic qt-5.
> 

Actually, we should probably depreciate it and mark it superseded by
qtbase for a while. Packages in channels won't have it ripped out, but
if/when they fail to build they'll find out that its modular qt only
now.

-- 
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: 833 bytes --]

  reply	other threads:[~2019-10-25 10:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-24 19:20 [bug#37908] [PATCH 0/2] Remove monolithic qt5 (and other unused package) Hartmut Goebel
2019-10-24 19:23 ` [bug#37908] [PATCH 1/2] gnu: Remove qtdeclarative-render2d Hartmut Goebel
2019-10-24 19:23   ` [bug#37908] [PATCH 2/2] gnu: Remove monolithic qt5 Hartmut Goebel
2019-10-25 10:34 ` [bug#37908] [PATCH 0/2] Remove monolithic qt5 (and other unused package) Efraim Flashner
2019-10-25 10:43   ` Efraim Flashner [this message]
2019-10-25 21:33     ` Ludovic Courtès
2019-10-28  9:06       ` Hartmut Goebel
2019-11-01 10:49         ` Ludovic Courtès
2019-11-01 12:18           ` Hartmut Goebel
2019-11-01 14:14             ` Ludovic Courtès
2019-11-01 14:39               ` Efraim Flashner
2019-11-01 16:09                 ` bug#37908: " Hartmut Goebel

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191025104300.GK15460@E5400 \
    --to=efraim@flashner.co.il \
    --cc=37908@debbugs.gnu.org \
    --cc=h.goebel@crazy-compilers.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.