The dialogs that depend on it, will depend on it and pull it in when
they are installed. If nothing in the base image already depends on it
there is no need for it to be there.

On 14/5/23 06:47, Bernhard Bloxberg wrote:

boredsquirrel reported a new issue against the project: SIG that you are following:
``
I layer it currently. Interesting is that it has libadwaita as a dependency.

It seems to be preinstalled on Silverblue, and even though it uses libadwaita I think for consistency it should be included in Kinoite too.

Many dialogs depend on it, as its a very useful tool for GUI scripting.

Currently:

libadwaita-1.3.2-1.fc38.x86_64 zenity-3.92.0-2.fc38.x86_64
``

To reply, visit the link below or just reply to this email
https://pagure.io/fedora-kde/SIG/issue/352

As much as possible, applications should be shipped as Flatpaks or run from a container/tooblox.

What functionality would this provide that is missing from the base image?

Given that Zenity is more of a workaround / development tool and that it creates GTK dialogs, I'll close this one.

Yes its a GTK application.

But how should apps requiring it install it along?

It can be used in small projects to GUIfy scripts. I think it is used in lots of projects not installable as an RPM.

Is there a universal alternative on KDE? Because KDialog is only for KDE so nobody uses that.

But how should apps requiring it install it along?

As a dependency.

It can be used in small projects to GUIfy scripts. I think it is used in lots of projects not installable as an RPM.

If scripts require it, they should 1) Recommend users install zenity on their system and 2) check for it and advise the user that it's not installed.

Yes its a GTK application.

But how should apps requiring it install it along?

It can be used in small projects to GUIfy scripts. I think it is used in lots of projects not installable as an RPM.

Is there a universal alternative on KDE? Because KDialog is only for KDE so nobody uses that.

Zenity is a GNOME project, just like KDialog is a KDE project. Whether people use one more than the other doesn't really matter here.

But how should apps requiring it install it along?

As a dependency.

It can be used in small projects to GUIfy scripts. I think it is used in lots of projects not installable as an RPM.

If scripts require it, they should 1) Recommend users install zenity on their system and 2) check for it and advise the user that it's not installed.

but then the lack of this small package would require the users to layer it.

The state today simply is that zenity is way more widely used. And especially for example in an easy guified setup script, the user isnt supposed to layer anything.

Why can't users run those from a toolbox?

What applications included in the base image need Zenity?

We can not include everything in the base image, we need to focus on the critical parts and let users run the rest from Flatpaks or containers.