October 2007 - YaST Development - openSUSE Mailing Lists

[yast-devel] policy-editor module help
by Justin Haygood 15 Oct '07

15 Oct '07

I'm currently working on the policy-editor module for YaST (to edit PolicyKit configuration), and I want some input on some of the design decisions: 1. I'm using python code for the loading and parsing of the policy description files (its XML, and DOM makes parsing XML a dream). The policy description files describes the actions, provides a (translateable) description, and sane defaults. That part I'm fine with, since I can use YCP to interact with and load the model from the python code. 2. The actual policies as defined by the system administrator is located in /etc/PolicyKit/PolicyKit.conf Now my question is, how should I go about generating this file? Should we use this file directly, or use sysconfig to generate the file dynamically, and potentially provide for a "local include" so that you can include custom policies not set via YaST? -- 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] odd behavior in yast installer
by Justin Haygood 15 Oct '07

15 Oct '07

When installing the OS, and using the online repos, it prefers the "online" version of the package over the local version, even if its the same package! I don't think this behavior is expected, or is it? -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 1

[yast-devel] yast-ui: Lack of const for code arrays
by Ricardo Cruz 12 Oct '07

12 Oct '07

Hi, On yast-ui headers, we have code as follows: virtual char *widgetClass() { return "YCheckBox"; } This results in a ton of warnings on newer versions of g++ (at least 4.2.1). This function names the class, while debugLabel() names the object, so the string should always be constructed like that. Let's just make the pointer const. Patch appended. Thanks, Ricardo

2 6

[yast-devel] Czech YaST2 team (Prague) meeting 2007-10-09
by Michal Zugec 10 Oct '07

10 Oct '07

Czech YaST2 team (Prague) meeting 2007-10-09 ============================================ Present: jkupec, jsrain, juhliarik, kmachalkova, locilka, lslezak, mvidner, mzugec Absent: dfiser, jsuchome Minutes: mzugec Next minutes: jkupec Meeting date ------------ There is an idea to move our YaST-meeting date from Tuesday to Wednesday because for some people this is more acceptable date. ITO --- Every YaST member has about one week of ITO. Now it's good time to use it ;-) GCC 4.3 ------- YaST was fixed to be compiled with new GCC 4.3 we have in autobuild. All developers - check your code, especially operators priorities. proxy ----- For proxy setting is used .curlrc for YaST, curl and libzypp but with different syntax (especially for "\"). This should be probably fixed in yast2&zypp. There was also discussion if put configuration as global for system (/etc/sysconfig/proxy) or for user "root". Mzugec will do research on freedesktop.org ncurses ------- Adaptation for mod_ui is in progress, kmachalkova is working on tables now. yast wiki --------- There is new wiki-page about setting wireless network in 1.st stage of installation. (Lukas - URL ?) upgrade ------- During upgrade from 10.2->10.3 there can be some problems because of disk renaming from hda to sda. Problem can occur when user use more partitions on more disks. Workaround exists : Before start upgrade, boot into 10.2 system and change mounting in storage module to mount-by-id SLEPOS ------ Locilka did script for migration of SLES (prosim detaily, nejak som si to nezapamatal) yast2-core ---------- There was fixed bug in yast2-core that y2base didn't finished after code ends with error, instead of it it tries to find and run client with same name in other yast directories (bug #330656). -- 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] Zypp Patterns
by Ricardo Cruz 10 Oct '07

10 Oct '07

Hey, libzypp Pattern's install_packages() is marked obsolete as of 10.3. yast-gtk keeps using it, and so does -qt. Can you guys point me to the new API? Thanks, Ricardo -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 4

[yast-devel] YaST / PolicyKit integration
by Justin Haygood 10 Oct '07

10 Oct '07

(For some background on PolicyKit, http://people.freedesktop.org/~david/polkit-spec.html is a good read). Basically.. here's an idea for openSUSE 11+. Make YaST use PolicyKit to determine if it does certain actions or not. This would grant the following: 1. YaST (at least Qt and GTK+) itself will run as the user. This would allow for many benefits, i.e., GUI code isn't run privileged, etc.. 2. The system administrator could allow certain modules to be run without a root password. 3. The actual programs doing the actions would be forced to be separated from the UI code (a good design anyway), with something like the system message bus (D-Bus) as the middle man. AppArmor can even be utilized by making the privileged helper programs that do the actual work only able to do what they are intended to be done. The split between the privileged helpers and the unprivileged UI can probably be made easier by some easy APIs integrated into YCP, etc.. I plan on learning on how to make YaST modules by writing a "System Policy Editor" which will manage PolicyKit policies. It seems to be a self-documenting XML format, that the policy editor can then parse and use to provide a nice easy to use policy editor. What do people think about this -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

5 8

[yast-devel] Rethinking the Progress Screen (Mockup)
by Viper550 09 Oct '07

09 Oct '07

Personally, I think that the progress screen in the Yast installer is a bit hard to understand at first glance. When I installed 10.3 into a VM today, I was sorta confused by the vertical sectioned progress bar, I was a bit confused about the overall progress until I learned that each section corresponded to each installation repository involved! Also, because of how everything was arranged, I was having trouble figuring out how far it was in installation. I personally thought that the progress display for package installation could be made more streamlined and easier to understand without having to recode it in Qt4 (lol). What I did for this mockup, was combine all the repositories involved in an installation into 2 categories, disc based repositories (like the installation discs, obviously), and Internet repositories. Progress for each section is still displayed separately, but it is shown alongside the corresponding repository instead of vaguely in a stack of progress bars. An Overall Progress bar is also added to make the progression through the installation more clear. Because this information is withheld from the repository progress, the specific repository each package came from is shown next to the name of the package). Installation and Download progress is imprinted directly on the progress bar (Gnome style). What I originally wanted to do, was to make the repository list into a Firefox Download Manager like array, where each repository came up in a scrollable box with an icon next to it (denoting the source of it - media or internet), with the name, package count, and size listed next to it with the progress bar below it. But, benJIman said something about us not being able to have a scrollbar there due to some "UI limitations" that I was not told about. After that, I had to get through the issues of having "overflow" problems on my original design due to this, so I got the bright idea to just roll all the repositories into 2 categories here to simplify it. http://bay01.imagebay.com/full_view.php?view=21451_opensuseinstallmock.png So, how do you like it? Viper550 p.s. I would have sent this much sooner....if I had not accidentally went to the oracle one. -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 5

[yast-devel] web interface
by Jordi Massaguer i Pla 09 Oct '07

09 Oct '07

Hi yast developers, I've just taken the yast survey and I am happy I've seen a question about having a web interface. For me this is very important. Actually, what it will be great is to use the webmin interface. Which are you thoughts about that? Can I be involved? jordi PD: I have some yast development experience. -- Jordi Massaguer i Pla openTrends Solucions i Sistemes, S.L. Torre Llacuna C/Llacuna 166, 10º 1ª A 08018 Barcelona Phone: (+34) 93 320 84 14 Fax: (+34) 93 300 35 27 -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 4

[yast-devel] warning: suggest parentheses around ...
by Martin Vidner 08 Oct '07

08 Oct '07

Hi hackers, with GCC 4.3, you may have seen these new* warnings. I suggest that you pay attention to them, as I have just found a long standing bug thanks to them. Can you spot it? :-) http://svn.opensuse.org/svn/yast/trunk/core/wfm/src/Y2CCWFM.cc Y2CCWFM::createInLevel if (strlen(name) > 4 && !strcmp(name + strlen(name) - 4, ".ycp")) try_it = true; else { struct stat buf; if (0 == stat(name, &buf)) { // Try it, if it is not executable if (S_ISREG(buf.st_mode) && buf.st_mode & S_IXOTH != S_IXOTH) try_it = true; } } if (!try_it) return 0; Use: RPMNAME=yast2-core; less /work/built/dists/all/beta-i386/packs-i386/$RPMNAME/$RPMNAME-*/Logfile* *) Well the warning is not actually new, but before 4.3 it only worked for gcc, not g++. -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- 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] build failures with COPYRIGHT.english
by Martin Vidner 03 Oct '07

03 Oct '07

Hi, some packages failed in autobuild because I removed a duplicated license file from the devtools. I have already fixed the packages in SVN, so please submit your package when you see appropriate. Sorry for the noise. They are: yast2 yast2-installation yast2-network yast2-nis-server yast2-pkg-bindings-devel-doc yast2-printer The bug was https://bugzilla.novell.com/show_bug.cgi?id=299144 -- Martin Vidner, YaST developer http://en.opensuse.org/User:Mvidner Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

1 0