[Top][All Lists]

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

Wayland Functionality for Jami

From: Wamm K . D .
Subject: Wayland Functionality for Jami
Date: Wed, 05 Oct 2022 15:52:45 -0500
User-agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM-LB/1.14.9 (Gojō) APEL-LB/10.8 EasyPG/1.0.0 Emacs/28.1 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO)

The Jami available in the repo.s, currently, causes an error about the
Wayland plugin for QT not being available.

While some app.s don't require this to be bundled with the app. –
apparently (I run into similar errors for Qutebrowser but installing
QTWayland fixes the issue) –, Jami does.

Building the package definition in the repo. exactly as is but with
QTWayland added as an additional ~input~ causes Jami to be able to be
used under Wayland perfectly.

So my question is, what would be the best means of updating this
package? Should QTWayland just get added to the ~inputs~, even for
users who aren't running Wayland? Or would it make sense to just
create a second Jami package definition (called =jami-wayland= or
something) that ~inherit~s the original Jami package and just adds
QTWayland to the ~inputs~? Or a third option?

reply via email to

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