- YaST Development

[yast-devel] update.ycp bug...
by Michael Meeks 18 Apr '07

18 Apr '07

Hi guys, So JP found a bug in update.ycp when run with yast2-gtk, I stopped this crashing yast2-gtk (which was daft), but it looks like there is an underlying issue: We create a Wizard dialog, and we add steps to it, but surely we should do: Wizard::OpenNextBackStepsDialog(); update.ycp:35 instead ? Of course, that rather changes the look, but we can at least see the steps :-) HTH, Michael. -- michael.meeks(a)novell.com <><, Pseudo Engineer, itinerant idiot -- 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] what is the official YaST home page URL?
by Johannes Meixner 18 Apr '07

18 Apr '07

Hello, I like to enter an URL for the yast2-scanner RPM which points to the official YaST home page. What is the official URL for it? I.e. an URL which does not change from time to time. Is it something like http://en.opensuse.org/YaST http://developer.novell.com/wiki/index.php/YaST http://forge.novell.com/modules/xfmod/project/?yast http://forgeftp.novell.com/yast/doc/SL10.2/index.html By the way: Searching for "yast" on http://www.novell.com/linux/ does not result anything which looks like a YaST home page. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany AG Nuernberg, HRB 16746, GF: Markus Rex -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 7

[yast-devel] Yast UI Future ideas
by jdd sur free 17 Apr '07

17 Apr '07

I wrote some ideas on the discussion page, is that the expected wayout? copy below jdd Hello, Good idea to open this page. Some essential though, for the beginning: It's essential to keep the ncurse UI with complete functionality. openSUSE is probably the only distribution giving an intelligent complete interface, very pleasant through ssh and low bandwith connection. second, YaST is two parts: first time install and system configuration. help is important at install time, but _on paper_ we _must_ keep YaST small to be able to install on oldfashionned hardware with minimal ram (for example). 10 years old computers are today perfectly usable and used even in our countries by money disabled people, very interested by the freeness of Linux. third, I personnally think the way YaST is showing the config at install time is must better than the way it shows it at system config time. I speak of the summary page with all the components in a window with links (and the "change" box at bottom) fourth, the YaST control center is un-consistent at least for the network devices. Why are them separated from the other hardware? fith, the most ennoying YaST lack is the systematic failing of network detect for the printers. I think I have never seen YaST detect an existing printer on my Linux+Windows net (I have from one to three printers available, depending on the period), and the wording is very difficult to understand (I know of "samba" protocol, not about the others) thanks jdd 05:08, 17 April 2007 (UTC) -- http://www.dodin.net Lucien Dodin, inventeur http://lucien.dodin.net/index.shtml -- 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 Future ideas
by Ricardo Cruz 16 Apr '07

16 Apr '07

Hi folks, Opened a wiki page for people to drop some thoughts and ideas with regard to Yast interface. Stop by, and drop yours. :) http://en.opensuse.org/Yast_UI_Future You may notice reply-to is set to the yast-devel mailing list. Please, reply there. Cheers, Ricardo -- 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] Updater applet for Gnome and KDE
by Duncan Mac-Vicar Prett 12 Apr '07

12 Apr '07

The openSUSE updater is a desktop applet which shows the user the available updates (patches). It is very light and simple as the real work is done by the YaST solver. This allows us to provide one applet per desktop, much like you have a a NetworkManager applet per desktop. The KDE applet was born last year as a Google SoC project. Today I imported the opensuseupdater KDE applet sources from berlios to svn.opensuse.org/svn/zypp. The gnome applet was already in the zypp repository. There is a new wiki page for both the KDE and Gnome applet. * http://en.opensuse.org/Updater_Applet The sources for both applets are located here: * http://svn.opensuse.org/svn/zypp/trunk/updater-gnome/ * http://svn.opensuse.org/svn/zypp/branches/SuSE-Linux-10_2-Branch/updater-kd… Also, there is a work branch for the KDE applet where a major refactoring is going on to cleanup legacy code from SoC, use cmake as build system and load the backends as KDE plugins. It will become trunk once it works: http://svn.opensuse.org/svn/zypp/branches/work/updater-kde-refactoring/upda… Just email me for any question! cheers -- Duncan Mac-Vicar Prett Novell :: SUSE R&D, Maxfeldstr. 5, 90409 Nürnberg GF: Markus Rex, HRB 16746 (AG Nürnberg) -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 12

[yast-devel] Editing Configuration of SuSEfirewall2 Services Defined by Package (FATE #300687)
by Lukas Ocilka 12 Apr '07

12 Apr '07

Hi, About: ------ YaST Firewall can already work with services defined by packages for several weeks, nevertheless is had just a read-only access. Some of you (for instance, ftp-server or http-server maintainers) allow users to configure ports on which the services listens or operates but enabling or disabling these services (ports) in firewall was quite limited. New Feature: ------------ Now, there is a new functionality in 'SuSEFirewallServices' module: * GetNeededPortsAndProtocols returns map of the current definition of the service * SetNeededPortsAndProtocols immediately changes the definition in configuration file You can find this new functionality in yast2-2.15.28 or SVN. Example of Usage: ----------------- - Services defined by package are stored in the /etc/sysconfig/SuSEfirewall2.d/services/ directory, copy the attached 'abc' file there - Save services-dbp.ycp script somewhere and run it by `/sbin/yast2 /path/toservices-dbp.ycp` - See the /var/log/YaST2/y2log Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic { import "SuSEFirewallServices"; string service = "service:abc"; map <string, list <string> > ports_used = SuSEFirewallServices::GetNeededPortsAndProtocols (service); y2milestone ("----------------------------------------------"); y2milestone ("GetNeededPortsAndProtocols: %1", ports_used); y2milestone ("----------------------------------------------"); list <string> tmp = ports_used["tcp_ports"]:[]; ports_used["tcp_ports"] = ports_used["udp_ports"]:[]; ports_used["udp_ports"] = ports_used["rpc_ports"]:[]; ports_used["rpc_ports"] = ports_used["ip_protocols"]:[]; ports_used["ip_protocols"] = ports_used["broadcast_ports"]:[]; ports_used["broadcast_ports"] = tmp; y2milestone ( "SetNeededPortsAndProtocols: %1", SuSEFirewallServices::SetNeededPortsAndProtocols ( service, ports_used ) ); ports_used = SuSEFirewallServices::GetNeededPortsAndProtocols (service); y2milestone ("----------------------------------------------"); y2milestone ("GetNeededPortsAndProtocols: %1", ports_used); y2milestone ("----------------------------------------------"); } # Do not edit this file as it's just a template and will be # overwritten on package updates! Copy to a new file instead. # # Only the variables TCP, UDP, RPC, IP and BROADCAST are allowed. # More may be supported in the future. # # For a more detailed description of the individual variables see # the comments for FW_SERVICES_*_EXT in /etc/sysconfig/SuSEfirewall2 # ## Name: abc service (probably) ## Description: opens ports for xx in order to allow dd # space separated list of allowed TCP ports TCP="was tcp" # space separated list of allowed UDP ports UDP="was udp" # space separated list of allowed RPC services RPC="was rpc" # space separated list of allowed IP protocols IP="was ip" # space separated list of allowed UDP broadcast ports BROADCAST="was broadcast"

1 0

[yast-devel] netcat dependency of yast2-core and -printer
by Marcus Meissner 12 Apr '07

12 Apr '07

Hi, We had yet another complaint that a customer does not want to install "netcat" for security reasons (no need to discuss), but we cannot even tell him to rpm -e it to quieten his paranoia because it is required by yast2-core and yast2-printer. yast2-core has a netcat dependency because it uses it to do some connect tests in the ag_hostnames agent. Is this specific agent still in use? yast2-printer has it in some tools, where it is unclear to me if they are run during regular usage. I wonder if we can get rid of the hard netcat dependency here. Ciao, Marcus -- Working, but not speaking, for the following german company: SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- 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] YCP exit code
by Benji Weber 11 Apr '07

11 Apr '07

Hi, Is it possible to return an exit code from a YCP module? I've tried returning a value from the top level block but exit code always remains 0. Use case: I would like to return a value from a module running as root to one not running as root. Thanks in advance. _ Benjamin Weber -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 3

[yast-devel] Package Search & Metapackage work
by Benji Weber 27 Mar '07

27 Mar '07

Greetings All, I understand that some have expressed an interest in the ideas I have proposed for a package search resource, and single click install with metapackages. ( For those who don't know what I'm talking about see http://en.opensuse.org/PKGSearch-design http://blogs.warwick.ac.uk/bweber/entry/package_search_developments/ http://blogs.warwick.ac.uk/bweber/entry/more_metapackage_possibilities/ ) So I thought I'd inject some life into this mailing list by bringing up the question of whether we can get some of the required infrastructure in place in time for 10.3. While we still have 3 months or so of development time before feature freeze. I know Martin Vidner was trying to work out how to get the package search service code I developed running. I have now created some scripts to simplify this , and updated the README file to explain all the steps needed to get this working. The updated version is at http://benjiweber.co.uk/src/re-write/pkgsearch.tar.gz So why would we want to put these things in place? With the package search and metapackage handing functionality in place - Users could easily locate software whatever repository it are located in, and whatever the package is named - They could install it with a single action without having to comprehend the concept of adding and removing repositories first. I think this would make our most frequently asked questions a non-issue. So enough of why we should do it, what needs to be done? - Confirm a design for the search service. - Agree on the schemas. - Agree where we can host the search services - Develop to a state where it can actually be made public. - Utilise the resource within the package management user interface - UI design work - Usability testing? - Confirm design for metapackages - Agree on format, xml schemas, can we bundle rpm files with schema to make ISV distribution easy etc. - libzypp support for using a repository only temporarily. - libzypp support for .repo files to enable identifying repository duplicates - Implement user interface for installing these, along with KDE/GNOME mime type file handlers to open the packages with the handler from links in web pages or clicking on the package on local filesystem. - Security issues (can we show warning & summary of changes to user before they su to root, to mitigate any potential issues from malicious metapackages. Hope that is enough to start some discussion. _ Benjamin Weber -- 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] Welcome to yast-devel!
by Jiri Srain 20 Mar '07

20 Mar '07

Hi! Welcome to the yast-devel mailinglist. This list is meant to discuss topics related to the YaST development. It should be possible to reach the YaST developers on this list. This list is not meant to provide any kind of support; it is meant for development-related discussions only. Have a lot of fun! -- Regards, Jiri Srain YaST Team Leader --------------------------------------------------------------------- SUSE LINUX, s.r.o. e-mail: jsrain(a)suse.cz Lihovarska 1060/12 tel: +420 284 028 959 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz

1 0