EasyBashGUI is a Bash functions library for *BSD and GNU/Linux that aims to give simple GUI functions using yad, gtkdialog, kdialog, zenity, Xdialog, gum, (c)dialog, whiptail or bash builtins depending on KDE or GNOME running or not, Yad/Gtkdialog/Xdialog installed or not and, eventually, X server running or not.
i already noted this, but ignored cos debian a good distro and alpine a faster minimal distro already allows to put files in arch-depend paths (lib or lib64 etc)
but open suse a crap rpm based distro like feladora becomes too much restrictive so i cannot generate a package from.. i tested using cmake also and never allows..
the pacakge from feladora, redhat or similar can be used, so i dont know but i open the issue to suggest more paths for the bashgui.lib files
so by example in /usr/lib for debian and alpine the path is valid, cos arch specific is /usr/lib/x86_64-linux-gnu but for open suse the /usr/lib is arch specific
Ok... Let's wait for an hint by them: obviously in a makefile we need a "standard" path, unless we build a tarball "distro-specific" (e.g.: easybashgui-OpenSUSE_13.0.tar.gz )...
hint: on open suse builds fails for OBS due this: https://en.opensuse.org/openSUSE:Packaging_checks#suse-filelist-forbidden-noarch
i already noted this, but ignored cos debian a good distro and alpine a faster minimal distro already allows to put files in arch-depend paths (lib or lib64 etc)
but open suse a crap rpm based distro like feladora becomes too much restrictive so i cannot generate a package from.. i tested using cmake also and never allows..
the pacakge from feladora, redhat or similar can be used, so i dont know but i open the issue to suggest more paths for the bashgui.lib files
so by example in /usr/lib for debian and alpine the path is valid, cos arch specific is /usr/lib/x86_64-linux-gnu but for open suse the /usr/lib is arch specific