unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Alexander Asteroth <alexander.asteroth@h-brs.de>
Cc: help-guix@gnu.org
Subject: Re: How to handle concurrent QT versions
Date: Tue, 28 Feb 2023 17:53:11 +0100	[thread overview]
Message-ID: <Y/4xd0gnw1zN7Ulu@jurong> (raw)
In-Reply-To: <87r0uaf2n7.fsf@h-brs.de>

Hello,

Am Tue, Feb 28, 2023 at 12:25:13PM +0100 schrieb Alexander Asteroth:
> since two month I didn't update my guix system now since I have a few
> self compiled softwares that depend on QT@5.15 (qtbase, etc.) which I
> need every day. Now version 6 of QT replaces 5 everywhere and whithout
> updating to 6 I cannot update a lot of other packages.

I would expect it to work out of the box. From what I see, the Qt5
libraries are called libQt5xxx.so. Supposedly the Qt6 libraries are
called differently (libQt6xxx.so?), so you should be able to install
both of them into the same profile.

Independently, software from Guix built with one or the other can be
installed at the same time: They will just point to different libraries
in the store, unless you also install the Qt libraries into your profile.

Andreas



  reply	other threads:[~2023-02-28 16:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 11:25 How to handle concurrent QT versions Alexander Asteroth
2023-02-28 16:53 ` Andreas Enge [this message]
2023-03-01  8:14   ` Alexander Asteroth
2023-03-01 13:15     ` Felix Lechner via
2023-03-02 10:11     ` Andreas Enge
2023-03-03  8:47       ` Alexander Asteroth
2023-03-03 14:45         ` 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=Y/4xd0gnw1zN7Ulu@jurong \
    --to=andreas@enge.fr \
    --cc=alexander.asteroth@h-brs.de \
    --cc=help-guix@gnu.org \
    /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.
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).