YaST Development October 2007

yast-devel@lists.opensuse.org

32 participants
35 discussions

by Martin Schmidkunz

Hi, when testing openSUSE 11.1/SLES 11 I came across a rather curious situation: many modules have already switched their label from Abort/OK(Accept, Finish...) to the style guide compliant Cancel/OK label. However in every case there is a third, inactive "Back" button included. This doesn't make sense as there is nothing to go back and the dialog is just an overview. I suppose this is due to many of you using wizard.ycp as base template for creating your module. What do you think about using the button box (http://lizards.opensuse.org/2008/08/28/button-order-in-yast-trying-to-make-…) instead of the buttons of wizard.ycp? In my opinion this would have the following advantages: * consistent button order in pop ups and in the module * user would not need to deal with an inactive button * button order in YaST would be consistent with the desktop used by the user What do you think about that issue? Cu, Martin -- Martin Schmidkunz User Experience Specialist martin.schmidkunz(a)novell.com +49 (0) 911 740 53-346 ----------------------------------------------------------------- SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg) ----------------------------------------------------------------- Novell, Inc. SUSE® Linux Enterprise 10 Your Linux is ready http://www.novell.com/linux -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

13 years, 9 months

[yast-devel] 3 questions about yast....

by Roberto Angelino

OK. First some background: My customer has written a sles9->sles10 live update installation script. I just ran it via ssh. It uses autoyast (the sles10 version) and it installs onto a clean partition (i.e., a partition that isn't running sles9). It works, but they've had to mess with some of the ycp files. Note this script is specialized to their nodes because they only ship 2-3 type of nodes. It's not a general purpose script. Here are the 3 questions they have (for sles10 version): 1) After yast completes installation (i.e., post-install), the fstab is created. What yast module makes this call? It has to be in yast2-installation, but I can't find the connection between the installation and yast2-storage where WriteFstab() lives. 2) How does yast determine what the source partition to mount is? 3) bootloader_finish.ycp breaks the install at the end. They got the install to work by commenting out everything in bootload_finish.ycp. What does this file do? Thanks -robert -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

14 years, 5 months

[yast-devel] Re: [opensuse-factory] YaST2 SSHD Module - Call for help/volunteers

by Lukas Ocilka

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lukas Ocilka wrote: > Robison, Jonathon (M.) napsal(a): >> Although you may be correct in that it needs polish, don't forget that this >> is a great step forward in getting CLI config tasks into YaST. Every >> marathon starts with the first step. >> >> Now if I could just get wpa_supplicant configuration into YaST . . . > >> See (and modify) http://en.opensuse.org/YaST_SSHD_Server/Enhancements_WIP I've filed some real enhancement request at this http://en.opensuse.org/YaST_SSHD_Server/Enhancements_WIP wiki page. The current YaST SSHD screenshots can be found here http://en.opensuse.org/YaST_SSHD_Server Some of enhancements are quite easy to do even if you don't known any programming language, what they actually need is just to think about the current wording and propose a better-understandable one. Thanks & Bye Lukas -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFHG1yIVSqMdRCqTiwRAgBzAKCZoAx4Hre8VuxtvGkkxGc/DY/8OwCglDwz seNqny1Q5oN1f1QCMvAKtTA= =HmZe -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

14 years, 9 months

[yast-devel] Building UI libs vs. zypp vs. dev. environment (Was: how to mark *.ybc file outdated?)

by Katarina Machalkova

Ahoj! > > I'm afraid I can't start mailing concise requests for improvement of y2 > > development environment. > > Reading through your mails, you are very well able to describe > whats wrong and what must be improved. > > So speak up and raise the topic ! Thats what yast-devel, > yast-internal, team meeting minutes, weekly reports and FATE are for. So I'm speaking up and rising the topic :) This time it has nothing to do with .ybc files, but with UI libs and zypp (and no, it's not about app layer at all ;-) ) The problem: * To test a bugfix, I need to build yast2-ncurses. * To build y2-ncurses, I need libzypp headers (happen to lose them somehow during numerous upgrades) * Tried libzypp svn checkout and then cmake & make, but oh my ... it wants to download tons of satsolver cr ... I mean, data ;-) * Trying to skip this by going directly into libzypp/zypp subdir, it complains about missing libsatsolver-devel * OK, trying to compile sat-solver stuff - no success, I miss some rpmdb stuff * I'm giving up and going to have a joint ;-) Had I done 'rpm -ivh --force libzypp-devel.rpm' (force, because otherwise I would need libzypp.rpm as well and would never get out of rpm dependency hell) at the very beginning, I'd save at least half an hour of time and quite a lot of nerves But that's not a system solution. After all, I'm fixin' just an error in UI, what the heck do I need sat-solver for? So, either I'm doing something wrong or something is rotten in the state of Denmark ... Would splitting yast2-ncurses (as well as yast2-qt) package into pure UI part and package-management part and building those two separately help? Would some 'install header files from this subdir only' tool in libzypp makefiles help? I don't know Anyway, I'm speaking up and raising the topic :) frozenB. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter

14 years, 9 months

[yast-devel] Yast2 search results differ from zypper search result

by Aniruddha

Searching with yast2 for kernel (not in description) yields only one kernel source (2.6.22.9). While searching with zypper reveals two kernel-source packages: # zypper search kernel | package | kernel-rt | 2.6.22.5-31 | x86_64 | package | kernel-rt_debug | 2.6.22.5-31 | x86_64 | package | kernel-source | 2.6.22.5-31 | x86_64 | package | kernel-source | 2.6.22.9-0.4 | x86_64 | package | kernel-syms | 2.6.22.5-31 | x86_64 | package | kernel-syms | 2.6.22.9-0.4 | x86_64 # yast [Filterv] [Actionsv] ┌───────────────────────────────────────────────────── │ │Name │Avail. Vers.│Inst. Vers.│ │ │kernel-bigsmp │2.6.22.9 │ │ │ │kernel-debug │2.6.22.5 │ │ │ i │kernel-default │2.6.22.9 │2.6.22.9 │ │ i │kernel-docs │2.6.22.5 │2.6.22.5 │ │ i │kernel-rt │2.6.22.5 │2.6.22.5 │ │ │kernel-rt_debug │2.6.22.5 │ │ │ i │kernel-source │2.6.22.9 │2.6.22.9 │ │ │kernel-syms │2.6.22.9 │ │ │ │kernel-vanilla │2.6.22.5 │ │ │ i │kernel-xen │2.6.22.9 │2.6.22.9 │ │ │kernel-xenpae │2.6.22.9 │ │ │ i │linux-kernel-headers │2.6.22 │2.6.22 │ │ i │linux-kernel-nutshell│1 │1 │ │ │nfs-kernel-server │1.1.0 │ │ │ -- Regards, Aniruddha Please adhere to the OpenSUSE_mailing_list_netiquette http://en.opensuse.org/OpenSUSE_mailing_list_netiquette -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

14 years, 9 months

[yast-devel] openSUSE 11.0 - Splitting YaST packages - Call for help

by Lukas Ocilka

Hi YaSTies, I've found (and I'm probably not alone), that RPM dependencies in YaST packages might cause cyclic/cross dependencies, sometimes even when building the packages. In the past, we were solving such issues by moving the YCP/Perl module, that was needed by two or more YaST RPMs, to yast2.rpm package. However, this seems to be something that can't last forever ;) The current yast2.rpm package is already quite big. I already did something similar for 10.2 but YaST is currently widely open and plenty of developers are familiar with YaST internal processes so it's not needed to be a one-man-show ;). My idea is simple: * First, check the current dependencies. Can't we just remove them? * Then, think about moving some shared code/modules to some RPM that is already requested by those which need to share it. * Think about splitting yast2.rpm into more packages (several YaST RPMs don't need all that stuff). * Splitting yast2-installation into two packages. * Some debugging tools or scripts would be helpful. What should we achieve? * Less dependencies * No more cyclic issues Of course, some dependencies need a longer discussion, some don't need to be expressed at all (for inst-sys, for instance). #yast IRC channel at Freenode seems to be very-well suitable for such discussion ;) So, who's interested in it :)? I am, of course :) Have a nice day Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic

14 years, 9 months

[yast-devel] [Fwd: [opensuse] yast squid module]

by Lukas Ocilka

Enjoy! ;) -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic

14 years, 9 months

[yast-devel] PackageKit

by Ricardo Cruz

Hi there, I was told of this project: http://www.packagekit.org/ They aim to do a common interface for package and patch management for all distributions, which just need to hook their package system as a backend. It doesn't seem to have a text interface, and it could be a problem with regard to the installation integration. It would still be nice to consider it. What do you think? Cheers, Ricardo -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

14 years, 9 months

[yast-devel] yast ncurses mode survey, my 2 cents

by Druid

Hi Yast People, Have been reading the wiki pages for the yast ncurses survey I was quite amazed by the answers on the survey (because they clearly didnt include the sysadmin usecase), and started answering them mentally. It went like this: * Who are the users who use text-mode YaST (yast2-ncurses)? sysadmins * Why do people use text-mode YaST? because they didnt install X in their servers * In which ways would they be hit/restricted if text-mode YaST were dropped? They would go to prague and kill you all, because they would miss useful features for administration. And no, command line interface doesnt replace it * What do people mostly miss in text-mode YaST? decent keybinding navigation, non-sluggish navigation with tab/shitft-tab/esc, taht sometimes lags or freezes a second or half second. So this is, I guess, what a suse sysadmin would answer (and my 2 cents). The ncurses is very neat, I can give instructions to newbie sysadmins, its consistent, they feel comfortable, people using other unix flavors that has those types of dialogs feel comfortable. Please, think of the sysadmins! =) Marcio Ferreira --- druid -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

14 years, 9 months

[yast-devel] Handle GUI and text-mode differently - yast ncurses survey

by Katarina Machalkova

Dear brothers and sisters in YaST, (some of you already discovered the wiki page on $subject, so here is a full explanation on what is this all about) One of discussion topics on our recent workshop was whether we should handle graphical UI differently from the text-mode. However, we found out that we don't know an exact answer to the question who are the users of the text-mode UI, why do they decide to use it, and if we decide to drop it, can we find any equivalent? In order to find some answers to at least some of the above questions, I decided to carry out a small, informal in-house survey among Czech openSUSE developers. The group was rather small and well, yes, developers are not exactly the representative sample of society, but they are human beings (most of them ;-) ), they are openSUSE users, and their opinion counts as well The detailed questionare can be found here: http://en.opensuse.org/YaST_Workshop_Prague_2007_Day_1/YaST_ncurses_survey#… Some of the q's were multiple-choice with one open-ended "Something else, please specify..." item, the others were entirely open-ended. What does this small survey reveal? * Text-mode users do not miss eye-candy, but - surprise, surprise ;-) they _do_ miss functionality, they miss more comfortable and intuitive navigation in UI. * They use text-mode because - It is usable even without X - It provides the same functionality as GUI - It is better choice for using over the network - It is faster and has lower memory requirements - and many more, see here: http://en.opensuse.org/YaST_Workshop_Prague_2007_Day_1/YaST_ncurses_survey#… The entire summary of this topic can be found on this page: http://en.opensuse.org/YaST_Workshop_Prague_2007_Day_1/Handle_graphical_and… which is a joint work of Jirka Suchomel, Lukas Ocilka and me. And there are 3 possible conclusions of our workshop discussion and this survey: * We should cater for needs of different types of users. We can make one UI an eye-candy for those users that want it, while keeping the other one simplistic, because its users want it to stay so. * While improving look&feel, we should keep in mind that users do need and do appreciate functional equivalency of all UIs * Having ncurses may limit us in certain aspects (no yellow-violet-pinkish eye-candy, no icons in every single table cell, low resolution and mouseless user,...), but there are other areas in which it gives us even more freedom instead of restricting us (we're independent of functional X server, certain web-browser, fast network connection, and we still can have well-usable and functionally equivalent UI). B. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter

14 years, 9 months

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

YaST Development October 2007