install repos are nice but (unfortunately) often not viable

[DJCrashdummy]

this is somehow a follow up on #3:

i found easybashgui because i was looking for an easy way to make my scripts work with different DEs.
in theory this solution is perfect (and having all the repos to install it on different distros is nice), but in practice having to add an external repo - beside installing extra software - just to have an abstraction layer for a dialog system which is already present on the system, is kind of a deal breaker. 😞

so IMHO to lower the bar for further/easier adoption, easybashgui should become available via default repos at least in the main distributions like Arch, Debain, Fedora etc. - AFAIK Flatpak wouldn't make sense at all... 🤨
for sure the best would be to have easybashgui installed by default... but well i'm just dreaming now. getting it in the default repos would be a (first) huge step forward.

[mckaygerhard]

Unfortunately the different policies from the linux distributions are so dumps and foolish

For example, in Debian, the bureaucracy is extremely high, and creating the package would end up being more than just a simple file with the instructions.

This is very different from Alpine and Arch, where a single file would build everything necessary.

Arch no matter the developers or etc whatever found of those rare conceited and very arrogant .. there is AUR, so always be a way to mantain in repos.. BUT: However, in the case of Alpine, there are a lot of woke users and people without a clear identity who use the software to create an identity; we would end up with a package very different from what is intended.

There is a script in EBG that is called "legacy" you can embed this on your project as second way.. or fully embed EBG on your project..

Sorry for that but YES this is the problem in linux .. too much stupid people, we have hotplug then hal then shitstemd and in future another and another.. we started with OSS, then ALSA and then esound/arts and then pulseshitaudio and then pipewire.. this does not happened so much in the OS of ignorants .. so called Windos

[mckaygerhard]

In resume that you request it always depends on the foolish distributions rules on each one! the always so called common problem in linux distribution of software

[DJCrashdummy]

well i'm not experienced at packaging (for different distributions), so i can't argue with any of that...

but one thing i want to add: it doesn't have to be all major distribution at once (let alone people will differ on what are major distributions), and not even all have to be packaged by this project itself.
perhaps starting with one or a few distributions with easy policies - and ideally many different (default) DEs - would be a good start to have more people easily use and appreciate EBG. and with time distro hoppers and admins who have to deal with more than this distro(s) may support getting EBG in others too... perhaps if they are already maintaining other packages, they might even package it themselves.

There is a script in EBG that is called "legacy" you can embed this on your project as second way.. or fully embed EBG on your project..

thanks for mentioning that... i'll have a look at it. 👍

[mckaygerhard]

it seems you dont understand! packaging of any software it depends of each upstream lilnux distro rules.. and in your case, cos mayor distributions are becoming so crap nowadays .. linux now looks like a M$ product!

That-s why we provide an automatic OBS repository.. we can also offers a downloable package as a solution .. i mean: on each new release you can download your specific package manually fron github .. so ? @vaisarger ? if this is an solution you @vaisarger must coordinate with me each new release!

[vaisarger]

Hi! I apologize for late reply... :)

First of all, thank you @DJCrashdummy for your interest.
You know, I tried in past years to propose to some distro packagers to include EBG... Some did it (you could find some older versions in their repos, some said "no" because I should have a sort of acquaintance -Debian-... Well, I gave up! :P
I thought that having an installable file with a simple "make install" it wouldn't be that difficult for a user to install EBG.
So since then I focused just on improving EBG.

Thank you @mckaygerhard for your effort to give a way to add a OBS repo... please, don't be angry if a user asks for a package, it's a legitimate request. I know, I know... actually you are angry for current Linux state... It's a mess!
Anyway....

@DJCrashdummy , if you really would like to help the project you could propose EBG to some distro packagers... You are welcome. :)

About the "legacy" script... Please, forget it.
It's just a demo, but

1. it's not updated with all the latest features,
2. it's not actually a script, but a wrapper I wrote to better demonstrate EBG's potential, for those who don't want to source in their own script, but want to use it only from the command line...
   But I repeat, it's not updated... I don't know if it still works, and in any case, it doesn't have all the latest EBG features.

In the end, it's just a "make install" and a "source easybashgui" ;)

[DJCrashdummy]

@vaisarger there is nothing to apologize for... and thank you for for releasing this FOSS!

if you really would like to help the project you could propose EBG to some distro packagers...

at least for now i'm spreading the gospel of EBG and if i get the chance to meaningfully suggest it for packaging, i'll do so.

I thought that having an installable file with a simple "make install" it wouldn't be that difficult for a user to install EBG.

well... it depends on the user let alone the circumstances:

• user with quite some knowledge: no big deal
• user with no clue but "supervision" of an advanced user (and the freedom to add 3rd-party repos): the repos are awesome!
• user with no clue and no advanced user at hand: somewhat difficult...
• user with an "immutable" system: you are screwed anyway as long as it isn't in the distributions repos

About the "legacy" script... Please, forget it.

what a bummer... ok, already done. 😑
but the "User module install" to ship it with my script still works as intended? - because it seems i have to go this route (if i really need EBG) to cover most cases, although then i will have to roll out updates more often...

[vaisarger]

I could, in future, work on the legacy script... so far it's not updated. If you put Easybashgui in your tarball (that is your script + EBG) and you make your script point to "easybashgui" file in your local directory there is no difference between EBG "system mode" and EBG "local mode". Files are the same: only files you could not find could be "Ok.xpm" and "Attenzione.xpm" those are just icons for Xdialog mode. For everything else all checks and functions are the same. In these days I'm going to holiday, anyway let me know if you have some problem, and when I'm back I try to study the issue... ;) Il giorno gio 16 lug 2026 alle ore 10:21 DJCrashdummy < ***@***.***> ha scritto:

…

*DJCrashdummy* left a comment (BashGui/easybashgui#48) <#48 (comment)> @vaisarger <https://github.com/vaisarger> there is nothing to apologize for... and thank you for for releasing this FOSS! if you really would like to help the project you could propose EBG to some distro packagers... at least for now i'm spreading the gospel of EBG and if i get the chance to meaningfully suggest it for packaging, i'll do so. I thought that having an installable file with a simple "make install" it wouldn't be that difficult for a user to install EBG. well... it depends on the user let alone the circumstances: - user with quite some knowledge: no big deal - user with no clue but "supervision" of an advanced user (and the freedom to add 3rd-party repos): the repos are awesome! - user with no clue and no advanced user at hand: somewhat difficult... - user with an "immutable" system: you are screwed anyway as long as it isn't in the distributions repos About the "legacy" script... Please, forget it. what a bummer... ok, already done. 😑 *but* the "User module install <https://github.com/BashGui/easybashgui/blob/master/docs/install.md#user-module-install>" to ship it with my script still works as intended? - because it seems i have to go this route (if i really need EBG) to cover most cases, although then i will have to roll out updates more often... — Reply to this email directly, view it on GitHub <#48?email_source=notifications&email_token=ABDFPQ3EBSK7FNEG7ETQYQD5FCGCDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJYHE3TAOJTGQ42M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-4989709349>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDFPQ3OAYILP3OCBLYQOX35FCGCDAVCNFSNUABEKJSXA33TNF2G64TZHMYTANBXGMZDMMZ3JFZXG5LFHM2DMMJSGI4DMMZQGKQXMAQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ABDFPQ6SHFNHZMLLQ4A5RSD5FCGCDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJYHE3TAOJTGQ42M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/ABDFPQY6JHO2UJDMYITVHYL5FCGCDA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIOJYHE3TAOJTGQ42M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[DJCrashdummy]

[...] there is no difference between EBG "system mode" and EBG "local mode". [...] only files you could not find [...] are just icons for Xdialog mode.

that's great to hear! ...if that's all (and it fails silently for the user), i'd say: let it be 2 missing icons. 😉

[...] let me know if you have some problem, and when I'm back I try to study the issue... ;)

well... for now i made do - once more - with libnotify for the current project.
let's see if it gets bigger and i need to switch or if i must use EBG for another project (and there is already one on the horizon for which this seems to be the case)... but both almost certainly won't happen before fall.

I could, in future, work on the legacy script... so far it's not updated.

@vaisarger so far i don't see a really big difference to the "local mode" aka. "user module"... but that being said, i haven't used even one of them (yet). 🤷

---

BTW: in the docs as a side-note i would suggest to use trap if possible for clean_temp in user mode.

[vaisarger]

Il giorno ven 17 lug 2026 alle ore 09:57 DJCrashdummy < ***@***.***> ha scritto:

*DJCrashdummy* left a comment (BashGui/easybashgui#48) <#48 (comment)> [...] there is no difference between EBG "system mode" and EBG "local mode". [...] only files you could not find [...] are just icons for Xdialog mode. that's great to hear! ...if that's all (and it fails silently for the user), i'd say: let it be 2 missing icons. 😉 [...] let me know if you have some problem, and when I'm back I try to study the issue... ;) well... for now i made do - once more - with libnotify for the current project. let's see if it gets bigger and i need to switch or if i must use EBG for another project (and there is already one on the horizon for which this seems to be the case)... but both almost certainly won't happen before fall.

EBG "notiy_message()" is a very reliable function: it's based on "notify-send" (that is very common tool often already installed), however there are *many* fallback substitutions in case "notiy-send" is not installed. See "notify_message()" in "easybashgui.lib" to realize... I strongly suggest you to use "notify_message" for your notifications... ;)

I could, in future, work on the legacy script... so far it's not updated. @vaisarger <https://github.com/vaisarger> so far i don't see a really big difference to the "local mode" aka. "user module"...

"local mode" is an other way to call "user module". From https://bashgui.github.io/easybashgui/#/docs/#system-wide-usage-vs-module-user-usage : *System wide usage vs module user usage* *If EBG is not installed you should have at least all the files in the same path as your main script, if you install it on the system you don't have to worry about this!* *A program/project that implements EBG and does not use same path from main script, can put the EBG script and files in another path, but structure must be in the same hierarchy indicated in the installation guide "Install path" section. <https://bashgui.github.io/easybashgui/#/docs/install.md#install-paths>* *The USER way must have full path to the endpoint or the files must be in the same path of the script you made:* *#!/bin/bash source ./easybashgui # .. code here clean_temp * *The SYSTEM way just need endpoint without path and the files must be in system paths, the script you made should look like:* *#!/bin/bash source easybashgui # .. code here * *The difference in modes is just two: first you noted that source endpoint does not have a path (in the USER mode is "./") and second the SYSTEM mode does not need to clean temporally files (in the USER mode is clean_temp).* *If easybashlib is present and successfully loaded, you can avoid last sentence of clean_temp to remove temporary files; otherwise DO NOT forget to write clean_temp at the end of all your scripts... ;-)*

but that being said, i haven't used even one of them (yet). 🤷 ------------------------------ BTW: in the docs as a side-note i would suggest to use trap if possible for clean_temp in user mode.

In "easybashlib" (If I remember well) it's used "trap" to avoid the need of "clean_temp" usage. Since normally "easybashlib" is loaded (sourcing "easybashgui"), then you don't need "clean_temp" usage. You still need "clean_temp" just if you source "easybashgui.lib" directly (that doesn't source "easybashlib"), for this reason you should not source easybashgui.lib directly. Source "easybashgui" instead, and then, you will not need "clean_temp". Ok???

…

— Reply to this email directly, view it on GitHub <#48?email_source=notifications&email_token=ABDFPQ7T2DJHKK32NPEMLH35FHL6JA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBQGAZTQOJQHA3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5000389086>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABDFPQ5ANIRLJVF4Q7HN4J35FHL6JAVCNFSNUABEKJSXA33TNF2G64TZHMYTANBXGMZDMMZ3JFZXG5LFHM2DMMJSGI4DMMZQGKQXMAQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/ABDFPQ7RXJTFLUIJQEOMMYL5FHL6JA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBQGAZTQOJQHA3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/ABDFPQ3DQ4WSQ46YYV52P3L5FHL6JA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBQGAZTQOJQHA3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

[mckaygerhard]

i am so proud to check that this documentation is hell yeah damn well done! the person that made it for sure is a great guy XD Okay, seriously now... @DJCrashdummy and anyone else interested, I want to recall and emphasize this: Look at https://github.com/doas-utils/doasudo .. a new fork/way from https://github.com/jirutka/doas-sudo-shim .. the project was a simpel script to use doas as sudo alternative, what happened ??, "doasudo" now required a skill person to compile and install.. as must be! cos "usage is not the same as manage" *When we make it "easy for those who don't know," we're devaluing and degrading the work of technical support people and project performance organization!. Roles are there for a reason!* Like that you @DJCrashdummy try to mantain simple and easy the things (like original doas-sudo-shim, cos doasudo overcomplicated all with stupid things for something simple) .. for that we can use the local way install.. but remember: installing a piece of software on the system isn't a user task. The word "user" simply means "someone who uses it," and with that, this whole issue loses its relevance. Its great if a piece of soft is easy to get it and use, *but "get it" is not the same as "use it" !* distributions should include EBG in their repositories since it doesn't require any real dependencies.. PS: My friend @vaisarger, I considered maybe all this as single-file script, but NO! EBG is well-structured and well-coded.!! we shouldn't betray the principles on which the free software world was born. Otherwise, we'd just be another dog like a piece of crak in the corporate machine empire!.

…

On Sat, Jul 18, 2026 at 11:15 AM Vittorio Cagnetta ***@***.***> wrote: *vaisarger* left a comment (BashGui/easybashgui#48) <#48 (comment)> Il giorno ven 17 lug 2026 alle ore 09:57 DJCrashdummy < ***@***.***> ha scritto: > *DJCrashdummy* left a comment (BashGui/easybashgui#48) > < #48 (comment)> > > [...] there is no difference between EBG "system mode" and EBG "local > mode". [...] only files you could not find [...] are just icons for Xdialog > mode. > > that's great to hear! ...if that's all (and it fails silently for the > user), i'd say: let it be 2 missing icons. 😉 > > [...] let me know if you have some problem, and when I'm back I try to > study the issue... ;) > > well... for now i made do - once more - with libnotify for the current > project. > let's see if it gets bigger and i need to switch or if i must use EBG for > another project (and there is already one on the horizon for which this > seems to be the case)... but both almost certainly won't happen before fall. > EBG "notiy_message()" is a very reliable function: it's based on "notiy-send" (that is very common tool often already installed), however there are *many* fallback substitutions in case "notiy-send" is not installed. See "notify_message()" in "easybashgui.lib" to realize... I strongly suggest you to use "notify_message" for your notifications... ;) > I could, in future, work on the legacy script... so far it's not updated. > > @vaisarger <https://github.com/vaisarger> so far i don't see a really big > difference to the "local mode" aka. "user module"... > "local mode" is an other way to call "user module". From https://bashgui.github.io/easybashgui/#/docs/#system-wide-usage-vs-module-user-usage : *System wide usage vs module user usage* *If EBG is not installed you should have at least all the files in the same path as your main script, if you install it on the system you don't have to worry about this!* *A program/project that implements EBG and does not use same path from main script, can put the EBG script and files in another path, but structure must be in the same hierarchy indicated in the installation guide "Install path" section. <https://bashgui.github.io/easybashgui/#/docs/install.md#install-paths>* *The USER way must have full path to the endpoint or the files must be in the same path of the script you made:* *#!/bin/bash source ./easybashgui # .. code here clean_temp * *The SYSTEM way just need endpoint without path and the files must be in system paths, the script you made should look like:* *#!/bin/bash source easybashgui # .. code here * *The difference in modes is just two: first you noted that source endpoint does not have a path (in the USER mode is "./") and second the SYSTEM mode does not need to clean temporally files (in the USER mode is clean_temp).* *If easybashlib is present and successfully loaded, you can avoid last sentence of clean_temp to remove temporary files; otherwise DO NOT forget to write clean_temp at the end of all your scripts... ;-)* > but that being said, i haven't used even one of them (yet). 🤷 > ------------------------------ > > BTW: in the docs as a side-note i would suggest to use trap if possible > for clean_temp in user mode. > In "easybashlib" (If I remember well) it's used "trap" to avoid the need of "clean_temp" usage. Since normally "easybashlib" is loaded (sourcing "easybashgui"), then you don't need "clean_temp" usage. You still need "clean_temp" just if you source "easybashgui.lib" directly (that doesn't source "easybashlib"), for this reason you should not source easybashgui.lib directly. Source "easybashgui" instead, and then, you will not need "clean_temp". Ok??? > — > Reply to this email directly, view it on GitHub > < #48?email_source=notifications&email_token=ABDFPQ7T2DJHKK32NPEMLH35FHL6JA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBQGAZTQOJQHA3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5000389086>, > or unsubscribe > < https://github.com/notifications/unsubscribe-auth/ABDFPQ5ANIRLJVF4Q7HN4J35FHL6JAVCNFSNUABEKJSXA33TNF2G64TZHMYTANBXGMZDMMZ3JFZXG5LFHM2DMMJSGI4DMMZQGKQXMAQ> > . > Triage notifications, keep track of coding agent tasks and review pull > requests on the go with GitHub Mobile for iOS > < https://github.com/notifications/mobile/ios/ABDFPQ7RXJTFLUIJQEOMMYL5FHL6JA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBQGAZTQOJQHA3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> > and Android > < https://github.com/notifications/mobile/android/ABDFPQ3DQ4WSQ46YYV52P3L5FHL6JA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBQGAZTQOJQHA3KM4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. > Download it today! > You are receiving this because you were mentioned.Message ID: > ***@***.***> > — Reply to this email directly, view it on GitHub <#48?email_source=notifications&email_token=AAL7XDAFNE6CNJ4JPO2S4P35FOH7ZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBRGE3TOMJQHEZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLDGN5XXIZLSL5RWY2LDNM#issuecomment-5011771093>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAL7XDDAVDBYGAYRVXJWKJL5FOH7ZAVCNFSNUABEKJSXA33TNF2G64TZHMYTANBXGMZDMMZ3JFZXG5LFHM2DMMJSGI4DMMZQGKQXMAQ> . Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AAL7XDFGGRUVHZ6UWV4L5TL5FOH7ZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBRGE3TOMJQHEZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJKTGN5XXIZLSL5UW64Y> and Android <https://github.com/notifications/mobile/android/AAL7XDBBJHALLX6LKVNCYR35FOH7ZA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTKMBRGE3TOMJQHEZ2M4TFMFZW63VHNVSW45DJN5XKKZLWMVXHJLTGN5XXIZLSL5QW4ZDSN5UWI>. Download it today! You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Lenz McKAY Gerardo (PICCORO) http://qgqlochekone.blogspot.com