[yast-devel] Classical YaST in Appliances: Choosing the UI
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I've just created a new JeOS appliance in SUSE Studio for testing purpose (YaST Backup bug). JeOS is known to have as few packages as possible. After selecting YaST Backup for installation, I've rather also checked whether I'll be actually able to run it, so searched for all YaST packages, especially the UI ones. And which one was selected? *yast2-gtk* OK, yast2.rpm requires yast2_ui and yast2-gtk, yast2-ncurses and yast2-qt all provide that symbol. Isn't there anything we could do about /better/ [1] selection [2]? Ideas? Opinions? Thx && Bye Lukas #1 'better' might be pretty subjective, I know. But this seems to be just alphabetically sorted list of solutions (for the first sight) #2 for example, KDE is installed -> Qt, GNOME/LXDE is installed -> GTK, neither of them (?) -> ncurses - -- Lukas Ocilka, Appliances Department, SUSE LINUX s.r.o. MD: Jeff Hawn, Jennifer Guild, Alena Hendrichova -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.16 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iD8DBQFOAvTtVSqMdRCqTiwRApcVAJ0aI3C01fxcJJSBIVUXduIqbLaFuQCfeIvy EIcQnPEenv7n64RHekoQiho= =GoF7 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On 06/23/2011 04:10 AM, Lukas Ocilka wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I've just created a new JeOS appliance in SUSE Studio for testing purpose (YaST Backup bug). JeOS is known to have as few packages as possible.
After selecting YaST Backup for installation, I've rather also checked whether I'll be actually able to run it, so searched for all YaST packages, especially the UI ones. And which one was selected? *yast2-gtk*
OK, yast2.rpm requires yast2_ui and yast2-gtk, yast2-ncurses and yast2-qt all provide that symbol. Isn't there anything we could do about /better/ [1] selection [2]? Ideas? Opinions?
IMHO, yast2_ui should require yast2-ncurses and recommend ast2-gtk and yast2-qt Robert -- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rschweikert@novell.com rschweikert@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
Robert Schweikert write:
On 06/23/2011 04:10 AM, Lukas Ocilka wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I've just created a new JeOS appliance in SUSE Studio for testing purpose (YaST Backup bug). JeOS is known to have as few packages as possible.
After selecting YaST Backup for installation, I've rather also checked whether I'll be actually able to run it, so searched for all YaST packages, especially the UI ones. And which one was selected? *yast2-gtk*
OK, yast2.rpm requires yast2_ui and yast2-gtk, yast2-ncurses and yast2-qt all provide that symbol. Isn't there anything we could do about /better/ [1] selection [2]? Ideas? Opinions?
IMHO, yast2_ui should require yast2-ncurses and recommend ast2-gtk and yast2-qt
Robert
This is not good idea, as for appliances you forget about webyast, which also provides yast_ui. And in this case install all ncurses libraries is useless as you configure appliance via studio and then via webyast. Pepa -- Josef Reidinger Appliance Toolkit team maintaining parts of webyast and SLMS author of rubygems - studio_api and net_observer (coauthor) -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
On 06/23/2011 06:16 AM, Josef Reidinger wrote:
Robert Schweikert write:
On 06/23/2011 04:10 AM, Lukas Ocilka wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hi,
I've just created a new JeOS appliance in SUSE Studio for testing purpose (YaST Backup bug). JeOS is known to have as few packages as possible.
After selecting YaST Backup for installation, I've rather also checked whether I'll be actually able to run it, so searched for all YaST packages, especially the UI ones. And which one was selected? *yast2-gtk*
OK, yast2.rpm requires yast2_ui and yast2-gtk, yast2-ncurses and yast2-qt all provide that symbol. Isn't there anything we could do about /better/ [1] selection [2]? Ideas? Opinions?
IMHO, yast2_ui should require yast2-ncurses and recommend ast2-gtk and yast2-qt
Robert
This is not good idea, as for appliances you forget about webyast, which also provides yast_ui. And in this case install all ncurses libraries is useless
Yes, but it should be the smallest set. Currently you not only get the ncurses but also gtk and qt packages. It appears to me that just pulling ncurses would be an improvement. Robert
-- Robert Schweikert MAY THE SOURCE BE WITH YOU SUSE-IBM Software Integration Center LINUX Tech Lead rschweikert@novell.com rschweikert@ca.ibm.com 781-464-8147 -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Dne 24.6.2011 16:25, Robert Schweikert napsal(a):
This is not good idea, as for appliances you forget about webyast, which also provides yast_ui. And in this case install all ncurses libraries is useless
Yes, but it should be the smallest set. Currently you not only get the ncurses but also gtk and qt packages. It appears to me that just pulling ncurses would be an improvement.
In fact, now you get GTK only. It's automatically selected by solver and you can select some other UI layer manually (in that case, GTK is automatically unselected) or select more, all. I'm only talking about the automatic selection, which looks a bit chaotic ~ or at least could be improved by some logic. Lukas -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/ iEYEARECAAYFAk4EpN4ACgkQVSqMdRCqTiwFOQCdFEQM+7+1V5euXhtPVQij4hM6 KSQAniL961cHav3xfMbligsIVWeanGGO =IsFr -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org For additional commands, e-mail: yast-devel+help@opensuse.org
participants (3)
-
Josef Reidinger
-
Lukas Ocilka
-
Robert Schweikert