-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debian package? #156
Comments
Hello Pjotrek, Peter,
You know, to the best of my knowledge nobody who collaborates with this github account (organization), makes packages for Debian and the default Debian repositories. If you're just interested in a deb package of gtkdialog, #152 might be of help? There's also the doglinux distro that is Debian based, includes gtkdialog and, I suppose, maintains some sort of deb repo. You might want to ask them, too. |
Thanks for the reply @step- :) I've already checked #152, and also compiled it right now on Xubuntu 20.04. Thanks for the tip about asking someone from "doglinux" (possibly in their forum). |
I wouldn't say it's a very active project, most recent changes are related to GTK+ 3 and Wayland migration. Personally, I use yad for any new code and keep gtkdialog around only for backward compatibility with code I can't remove easily. |
I added this package to Bodhi Linux 7. We have a Debian version so you can find the Bookworm version on our b7debbie repo. There is also a Ubuntu 22.04 version here. Both versions are at the latest git commit, and the qtkdialog-doc includes the info file and two example escripts have been patched to ensure they work with Debian/Ubuntu. I have NOT tested all the examples tho, just noticed those two. |
Hi everyone! 😃
I was wondering if gtkdialog could be packaged for Debian (again)? 😇
In 2009-12-08 it was removed from Debian Unstable, given the following reason:
Since gtkdialog has recent releases and seems to be active - I was curious to know if there's any chance of getting it back into default repositories?
Thank you very much in advance.
The text was updated successfully, but these errors were encountered: