October 2008 - YaST Development - openSUSE Mailing Lists

[yast-devel] Czech YaST2 team (Prague) meeting 2008-10-23
by Ladislav Slezak 29 Oct '08

29 Oct '08

Prague YaST Team Meeting 2008-10-23 =================================== Present: jkupec, jreidinger, juhliarik, jsrain, jsuchome, kmachalkova, locilka, lslezak, mzugec Absent: jsuchome, mvidner All developers were fixing bugs, here are the most important changes: - zypper displays product license (bnc#372386) - showexports agent has been moved from yast2-nfs-client to yast2 - yast2-wagon can update itself before updating the product - storage proposal uses PackagesProposal module - the deadline for the yast mascot has been moved to November 09 (http://en.opensuse.org/Marketing_Team/YaST_Contest) -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak(a)suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Playing with YaST dialog sizes
by Duncan Mac-Vicar P. 24 Oct '08

24 Oct '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Something I don't like from YaST-qt is the default size of dialogs (matter of taste). yast2-gtk handles it a bit better, but still not perfect. After the bug where yast2-qt did not fit on subnotebooks I got inspired to do some experiments with yast-qt size. It seems yast2-qt uses sizeHint for all widgets, except for the topmost, which is calculated artificially using the screen size, which results in lot of blank space and I have to turn my sight 10 meters down from the only line of text to the point I see the buttons (yes, I like to exaggerate...) yast2-gtk looks more fancy in this aspect, and delegates more hints to the toolkit, but the height is also too big. I attach some screenshots with yast2-sudo-big (original yast2-qt) and the same ones in a modified yast2-qt ( yast-sudo-small* ) I think the ideal situation is something in the middle. For example, my modified yast2-qt basically uses the minimum space possible, which is also not the answer, however the wizard looks much nicer in small (better said, enough) size. May be some better algorithm which does not use the screen size, but basically the minimal space needed plus some buffer so it does not look really packed. Just wanted to start a discussion on this "taste". Duncan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iEYEARECAAYFAkj91HUACgkQzR62qWZ+QtG/SQCffc6caGR7MMGNPUwLLN/10Bi1 1i4AnR3dxe1cDH35zsJddDghohcCTWNs =Yrim -----END PGP SIGNATURE-----

6 11

[yast-devel] buttons buttons buttons
by Martin Schmidkunz 24 Oct '08

24 Oct '08

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

3 6

[yast-devel] YaST2 Team Meeting 2008-10-17
by Lukas Ocilka 23 Oct '08

23 Oct '08

YaST2 Team Meeting 2008-10-17 ============================= Present: j(kupec|reidinger|srain|suchome|uhliarik), l(ocilka|slezak), mzugec Absent: kmachalkova, mvidner Table of Contents ----------------- 1.) Licenses in Repositories (zypper) 2.) Add-On Creator 3.) Product Creator 4.) Package Bindings 1.) Licenses in Repositories (zypper) ------------------------------------- zypper has to handle the stored product/repository licenses while adding or using repositories. Accepting the license is required for a repository to be used. An information about accepted license will be stored to prevent from requiring to accept it over and over again. 2.) Add-On Creator ------------------ Products are still quite vaguely defined. Add-On creator needs a definitive agreement on how the products are going to be created (metadata, formats ...). 3.) Product Creator ------------------- Product created without being signed automatically add insecure=1 Linuxrc parameter. Otherwise the product would be hardly usable because of Linuxrc complaining all the time. This option will be well-described in the Product Creator UI. See also http://en.opensuse.org/Linuxrc (option Insecure). 4.) Package Bindings -------------------- PB will offer functions to download and check signed repository files via libzypp. The function is: Pkg::SourceProvideSignedFile (integer repoid, integer medium, string filename, boolean optional) (bnc#409927). -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.

1 0

[yast-devel] YaST Contest - The last day to submit your ideas
by Lukas Ocilka 20 Oct '08

20 Oct '08

Hi, Today is the last day you can submit your ideas on how the YaST Mascot should look like and the YaST Mascot name. The judging will begin on October 21, and the winner will be announced on October 27. See http://en.opensuse.org/Marketing_Team/YaST_Contest for details and add your ideas to the Gallery section. Bye & Thanks Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.

1 0

[yast-devel] Nürnberg YaST team meeting 14.10.2008
by Duncan Mac-Vicar Prett 14 Oct '08

14 Oct '08

Nürnberg YaST team meeting 14.10.2008 present: aorlovskyy, aschnell, dmacvicar, gs, jdsn, ma, mantel, schubi, sh, snwint, tgoettlicher minutes: mantel - libzypp was broken the last days due to satsolver change (see below) so no last version could be submitted for current beta. This means especially that some bugs (like pattern selection crash) may reappear unless we get a late one accepted. The bugs are already fixed in svn though. - the file format for the SAT solver has been re-designed. Almost everything is fine again now, according to Michael Andres. libzypp testsuite at 99%. - tgoettlicher: most package kit problems are solved. testing will continue - storage: still some bugs in the queue - registration is finished now. adapted to suseRegister changes. It only get repository changes from suseRegister, and perform them using libzypp, via pkg-bindings, so ZYpp access is not reentrant anymore, and callbacks are honored. - smolt module has change requests that can't be changed at this point. There is no automatic upload of hardware profile data - the ncurses problem with black artefacts is still unsolved. Seems to be a bug in the kernel console driver. For now a workaround in yast2-ncurses is being used - Duncan wants a complete automatic rebuild of YaST2 on every check in. Unsolved problem are the cyclic dependencies of YaST. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] feedback from new yast partitioner
by Frederico Recsky 10 Oct '08

10 Oct '08

Hi, I've some feedback from new installer partitioner, and I'm a old user that uses a lot the old model. Normally I use the "Custom Partitioning (fox experts)" option and everything here is about it. In new partitioner, I see a list of my discs and partitions in a area "Available Storage" , and I click in one, selecting, and don't see nothing to edit, or some action to do. After a few time I go to side nav menu "System View" click in hard discs , my /dev/sda . These goes to Overview . Now I go to Partitions and find my "old screen" with Add.. Edit.. Resize and Delete... Also , after I discover that a double click in a partition or disc in the first screen goes also to partitions "old screen". To me it was easy when a see the list, select one and just choose "edit" or the action that I want. By the way the new partitioner gives me a real nice vision when I have nfs, LVM and another things like crypt and RAID. Also the "Settings" option, like "of mount by"" and "visible information" is useful. My suggestion is that you can keep the actions in bottom of the list to direct edit the things. Cheers -- ____________________________ Frederico Recsky Linux User: #253572 http://www.fred.eti.br http://www.perl.org.br -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 2

[yast-devel] JFYI: 'the big solv data change' - satsolver and zypp are currently broken
by Michael Andres 09 Oct '08

09 Oct '08

Hi! The latest satsolver in svn::trunk is broken, and libzypp is already adapted to the new interfaces. So currently everything compiles, but creation of solvfiles frequently fails. And maybe other things too. AFAIK revision 11278 is the last stable one. -- cu, Michael Andres +------------------------------------------------------------------+ Key fingerprint = 2DFA 5D73 18B1 E7EF A862 27AC 3FB8 9E3A 27C6 B0E4 +------------------------------------------------------------------+ Michael Andres YaST Development ma(a)novell.com SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) Maxfeldstrasse 5, D-90409 Nuernberg, Germany, ++49 (0)911 - 740 53-0 +------------------------------------------------------------------+ -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] Minutes of Nürnberg YaST meeting 2008-10-07
by Arvin Schnell 07 Oct '08

07 Oct '08

Minutes of Nürnberg YaST meeting 2008-10-07 ------------------------------------------- Present: aschnell, dmacvicar, gs, jdsn, ma, mantel, schubi, sh, snwint, tgoettlicher Minutes: aschnell - Beta 3 deadline is coming. - Usual complains about the amount of bug reports and the missing time between betas to fix them. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0

[yast-devel] 'remove' builtin: strange behavior?
by Stanislav Visnovsky 07 Oct '08

07 Oct '08

Hi! During bug fixing, Jozo came with interesting observation: the default behavior of 'remove' builtin for maps if a map does not contain key, is strange. Documentation: "Remove the value with the key KEY from a map. Returns nil if the key is invalid." The definition for list is similar. So, this means the following code will break quite a bit, if "this key" does not exist. a = remove( a, "this key" ) The proposal is to change the behavior to return the original (unchanged) map/list for CODE11 (openSUSE >= 11.1). Seems code in SVN seems to be quite OK (either uses haskey() or is safe by other means, or broken just because of this behavior ;-)) Any comments or objections? Stano -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 2