[opensuse-factory] Making space for yast-gtk
Hey there, I understand that you guys don't go with Yast-GTK by default (the package selector should still be loved for a bit longer :)), but it would be nice if you did the needed arrangement to /sbin/yast2, so if people choose to install it and are using Gnome/XFCE, that frontend is used. You need to start by adding a check_gtk function to /usr/lib/YaST2/bin/yast2-funcs. Just copy check_qt and change the value of Y2_QT to $plugindir/libpy2gtk.so.2 . You probably also want to rename that variable. ;) The /sbin/yast2 on factory is probably different than the one from 10.1, since that one is ugly and there is even an indication that reads "TODO: (...) refactor after release". In any case, one just needs to search for "qt" and hack there. Test it well to make sure it fallbacks nicely. 10.1 changes would be like: - if [ -z "$DISPLAY" ] || ! check_qt ; then + if [ -z "$DISPLAY" ] || (! check_qt && ! check_gtk); then (...) - $ybindir/y2base $module "$@" qt "$Y2_GEOMETRY" $Y2QT_ARGS + FRONTEND="qt" + if check_gtk && (echo $WINDOWMANAGER | grep -qi "gnome" || \ + echo $WINDOWMANAGER | grep -qi "xfce" || \ + ! check_qt) ; then + FRONTEND="gtk" + fi + $ybindir/y2base $module "$@" $FRONTEND "$Y2_GEOMETRY" $Y2QT_ARGS Now with the Novell's Gnome menu, you should be able to open a window with the Yast setup tools, rather than using y2controlcenter. You are probably already doing this, no? It would also be cool if you could ship with a yast-gtk rpm somewhere in the cds, so people could install it easy. Cheers, Ricardo -- If I had a plantation in Georgia and a home in Hell, I'd sell the plantation and go home. -- Eugene P. Gallagher --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi Ricardo, On Fri, 22 Sep 2006, Ricardo Cruz wrote:
I understand that you guys don't go with Yast-GTK by default (the package selector should still be loved for a bit longer :)), but it would be nice if you did the needed arrangement to /sbin/yast2, so if people choose to install it and are using Gnome/XFCE, that frontend is used.
Right ;)
You need to start by adding a check_gtk function to /usr/lib/YaST2/bin/yast2-funcs. Just copy check_qt and change the value of Y2_QT to $plugindir/libpy2gtk.so.2 . You probably also want to rename that variable. ;)
The /sbin/yast2 on factory is probably different than the one from 10.1, since that one is ugly and there is even an indication that reads "TODO: (...) refactor after release". In any case, one just needs to search for "qt" and hack there. Test it well to make sure it fallbacks nicely.
10.1 changes would be like: - if [ -z "$DISPLAY" ] || ! check_qt ; then + if [ -z "$DISPLAY" ] || (! check_qt && ! check_gtk); then
(...)
- $ybindir/y2base $module "$@" qt "$Y2_GEOMETRY" $Y2QT_ARGS + FRONTEND="qt" + if check_gtk && (echo $WINDOWMANAGER | grep -qi "gnome" || \ + echo $WINDOWMANAGER | grep -qi "xfce" || \ + ! check_qt) ; then + FRONTEND="gtk" + fi + $ybindir/y2base $module "$@" $FRONTEND "$Y2_GEOMETRY" $Y2QT_ARGS
Would it be possible for you to grab the latests copy of yast rpms from Factory (http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/sr...) and provide a patch to those packages that need to be changed via bugzilla? Regards Christoph --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Em Sexta, 22 de Setembro de 2006 10:54, o Christoph Thiel escreveu:
Would it be possible for you to grab the latests copy of yast rpms from Factory (http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/ src/) and provide a patch to those packages that need to be changed via bugzilla?
Okay. The exactly same /sbin/yast2 is used, so those changes apply. Added to buzilla at: https://bugzilla.novell.com/show_bug.cgi?id=207653 Would be nice to re-factor that /sbin/yast2. I will try to come up with something and contact it's maintainers. Anyway, that would be due to a following release so we can test it properly... Cheers, Ricardo
Regards Christoph
-- There are no data that cannot be plotted on a straight line if the axis are chosen correctly. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
On 2006-09-22 04:23:18 +0100, Ricardo Cruz wrote:
- $ybindir/y2base $module "$@" qt "$Y2_GEOMETRY" $Y2QT_ARGS + FRONTEND="qt" + if check_gtk && (echo $WINDOWMANAGER | grep -qi "gnome" || \ + echo $WINDOWMANAGER | grep -qi "xfce" || \ + ! check_qt) ; then + FRONTEND="gtk" + fi + $ybindir/y2base $module "$@" $FRONTEND "$Y2_GEOMETRY" $Y2QT_ARGS
i wouldnt blindly force xfce users to use the gtk version. this should be configurable. maybe a /etc/sysconfig/yast2 is needed darix -- openSUSE - SUSE Linux is my linux openSUSE is good for you www.opensuse.org --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hi Ricardo, Ricardo Cruz schrieb:
I understand that you guys don't go with Yast-GTK by default (the package selector should still be loved for a bit longer :)), but it would be nice if you did the needed arrangement to /sbin/yast2, so if people choose to install it and are using Gnome/XFCE, that frontend is used.
what do you think about adding a a possibility to override the auto-guessed setting. Maybe a setting YAST2_PREFERRED_FRONTEND somewhere in /etc/sysconfig with these values: auto: Guess the best matching of the installed frontends for the current environment, i.e. gtk for GNOME, qt for KDE and maybe fvwm2, ncurses if there's no X server. This should be the default. gtk: Use gtk if there's an X server even if KDE is running, fall back to ncurses if there's no X server. qt: Use qt if there's an X server even if GNOME is running, fall back to ncurses if there's no X server. ncurses: Use ncurses even if there's an X server running. Possible use case: GNOME is slightly broken in Factory right now, I'm using KDE therefore but still want to test yast2-gtk ;-) Another question (slightly off topic, sorry): How and where do I report bugs involving yast2-gtk? bugzilla.novell.com? Which information is needed - just the usual /var/log/YaST2, something else? Whom do I assign this to? Andreas Hanke --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Em Sexta, 22 de Setembro de 2006 15:13, o Andreas Hanke escreveu:
Hi Ricardo,
Ricardo Cruz schrieb:
I understand that you guys don't go with Yast-GTK by default (the package selector should still be loved for a bit longer :)), but it would be nice if you did the needed arrangement to /sbin/yast2, so if people choose to install it and are using Gnome/XFCE, that frontend is used.
what do you think about adding a a possibility to override the auto-guessed setting. Maybe a setting YAST2_PREFERRED_FRONTEND somewhere in /etc/sysconfig with these values:
If people would like that, it doesn't hurt to have... But it may make more sense to make that user specific, no? Having such a option in a file under ~/.yast2/. But we can just as well eat from both cakes; just load both files from the /sbin/yast2 script and, if ~/.yast2/frontend exists and the option variable is set, it would overrule the global setting. Anyway, I don't currently have the opportunity to follow the factory development, so that's out of my scope. Also, since yast-gtk isn't installed by the Gnome pattern or any other, it will just be installed if the user chooses to, so it isn't something we need to make ready for this release.
auto: Guess the best matching of the installed frontends for the current environment, i.e. gtk for GNOME, qt for KDE and maybe fvwm2 Actually it may make more sense to use the GTK frontend on FVWM. FVWM seems to have some GTK+ hooks that make them use its colors and more.
Possible use case: GNOME is slightly broken in Factory right now, I'm using KDE therefore but still want to test yast2-gtk ;-)
Okay. By the way, you can always test it by going directly to the source rather than using the yast2 launcher. That is, for the printers setup tool: kdesu /usr/lib/YaST2/bin/y2base /usr/share/YaST2/clients/printer.ycp gtk Or fooling yast2 script by doing: xhost + localhost su - WINDOWMANAGER=gnome yast2 Notice that any GTK application in Suse KDE is pretty ugly. It uses a theme that emulates the KDE one, but it has some problems like using big fonts and etc. Also, yast-gtk look is designed to feel like the interface provided by GtkAssistance (that will obsolete GnomeDruid), which is used by Gnome setup tools and I believe will be by XFCE as well. So, it will feel pretty alien elsewhere. Not that yast-qt feels much better in KDE. ;) Which btw I would vote to add a kde feeling to it and integrate it on kcontrol for a future release.
Another question (slightly off topic, sorry): How and where do I report bugs involving yast2-gtk? bugzilla.novell.com? Which information is needed - just the usual /var/log/YaST2, something else? Whom do I assign this to?
I don't know how to work with bugzilla much.. The other mail bug report was my first experience with it actually. :/ There is a YaST section... I guess we probably should use that, because the user doesn't necessarly know if its the interface that is not showing the right information or the backend that is providing false information. I don't really want to have to go check the bugzilla website and look for new bugs. Is there any mechanisms so that I can get report notifications to Yast by email? Then I could even set a filter on text like "interface" and "gtk" to read those more carefully. Meanwhile, you may email to the maintainers listed on AUTHORS. Cheers, Ricardo
Andreas Hanke
-- New crypt. See /usr/news/crypt. --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Hello, Am Freitag, 22. September 2006 17:14 schrieb Ricardo Cruz:
Em Sexta, 22 de Setembro de 2006 15:13, o Andreas Hanke escreveu:
what do you think about adding a a possibility to override the auto-guessed setting. Maybe a setting YAST2_PREFERRED_FRONTEND somewhere in /etc/sysconfig with these values:
If people would like that, it doesn't hurt to have... But it may make more sense to make that user specific, no? [...]
Running YaST as user doesn't make much sence because the lack of permissions, so a system-wide setting won't be a real problem IMHO ;-)
Not that yast-qt feels much better in KDE. ;)
It's hard to make it better with such a general "bugreport" ;-) Where do you see problems?
Which btw I would vote to add a kde feeling to it and integrate it on kcontrol for a future release.
YaST was already embedded in kcontrol some time ago, but removed again. Reason IIRC: You can close kcontrol at any time (killing YaST) - with causes "funny" effects to YaST or your system (just imagine you close/kill it while installing packages...) Regards, Christian Boltz -- Linux ist ein tolles Dings..... Es zeigt mir jeden Tag wieder völlig unaufdringlich meine Grenzen, und zeigt mir was ich alles noch nicht weiß.... [Axel Birndt in suse-linux] --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
Christian Boltz wrote:
Hello,
Am Freitag, 22. September 2006 17:14 schrieb Ricardo Cruz:
Em Sexta, 22 de Setembro de 2006 15:13, o Andreas Hanke escreveu:
what do you think about adding a a possibility to override the auto-guessed setting. Maybe a setting YAST2_PREFERRED_FRONTEND somewhere in /etc/sysconfig with these values: If people would like that, it doesn't hurt to have... But it may make more sense to make that user specific, no? [...]
Running YaST as user doesn't make much sence because the lack of permissions, so a system-wide setting won't be a real problem IMHO ;-)
YaST has been designed to run as either 'root' or 'user'. Actually, you don't need write permissions for every case of use. Sometimes read-only is enough. BTW: e.g., backup could work for all users. Lukas
Dňa Pi 22. September 2006 16:13 Andreas Hanke napísal:
Hi Ricardo,
Ricardo Cruz schrieb:
I understand that you guys don't go with Yast-GTK by default (the package selector should still be loved for a bit longer :)), but it would be nice if you did the needed arrangement to /sbin/yast2, so if people choose to install it and are using Gnome/XFCE, that frontend is used.
what do you think about adding a a possibility to override the auto-guessed setting. Maybe a setting YAST2_PREFERRED_FRONTEND somewhere in /etc/sysconfig with these values:
auto: Guess the best matching of the installed frontends for the current environment, i.e. gtk for GNOME, qt for KDE and maybe fvwm2, ncurses if there's no X server. This should be the default.
gtk: Use gtk if there's an X server even if KDE is running, fall back to ncurses if there's no X server.
qt: Use qt if there's an X server even if GNOME is running, fall back to ncurses if there's no X server.
ncurses: Use ncurses even if there's an X server running.
I'd suggest to create '/etc/sysconfig/YaST' for that. But we also already have /etc/YaST2/, where it's possible to configure YaST somewhat. Stano --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org
participants (7)
-
Andreas Hanke -
Christian Boltz -
Christoph Thiel -
Lukas Ocilka -
Marcus Rueckert -
Ricardo Cruz -
Stanislav Visnovsky