* Wayland Functionality for Jami @ 2022-10-05 20:52 ` Wamm K. D. 2022-10-18 18:25 ` Jaft 0 siblings, 1 reply; 2+ messages in thread From: Wamm K. D. @ 2022-10-05 20:52 UTC (permalink / raw) To: help-guix 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? ^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Wayland Functionality for Jami 2022-10-05 20:52 ` Wayland Functionality for Jami Wamm K. D. @ 2022-10-18 18:25 ` Jaft 0 siblings, 0 replies; 2+ messages in thread From: Jaft @ 2022-10-18 18:25 UTC (permalink / raw) To: help-guix@gnu.org Bumping this, just in case. On Wednesday, October 5, 2022 at 03:52:49 PM CDT, Wamm K. D. <jaft.r@outlook.com> wrote: 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? ^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-10-18 18:49 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <BY5PR07MB7029CB7929728480BF698A9B995D9.ref@BY5PR07MB7029.namprd07.prod.outlook.com>
2022-10-05 20:52 ` Wayland Functionality for Jami Wamm K. D.
2022-10-18 18:25 ` Jaft
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.