June 2008 - YaST Development - openSUSE Mailing Lists

[yast-devel] Request for new Builtin
by Arvin Schnell 13 Jun '08

13 Jun '08

Hi, it's ITO Friday again and I would like to add a tiny builtin to YCP. integer::range(integer n) integer::range(integer s, integer n) It produces a list with the integers from 0 or s to n-1 (as known from the Python range builtin). integer::range(3) -> [ 0, 1, 2 ] integer::range(1, 5) -> [ 1, 2, 3, 4 ] It's useful to iterate over a sequence of numbers (like with a 'for' in C), e.g.: foreach(integer i, integer::range(size(addresses)), { y2milestone("Address No %1 is %2", i+1, addresses[i]); }); This is rather clumsy without range. Comments? ciao Arvin -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

4 6

[yast-devel] New tag in YCP Modules
by Lukas Ocilka 13 Jun '08

13 Jun '08

Hi, I've just implemented a new functionality in ycpdoc that offers possibility to hide an internal YCP module from YaST Generated Documentation (bnc #344926). What was the reason? Currently, there are 299 modules documented for openSUSE 11.0. See: http://forgeftp.novell.com/yast/doc/SL11.0/modules/ But a lot of them are just for internal/one-module purpose. It's hard to browse through all those modules while searching for 'the one' you want. By now (effectively 11.1 Alpha0/+) you can insert --- cut --- * * Internal * --- cut --- into your YCP module header and it will be omitted in when the next round of documentation-build is done. For example, see: http://svn.opensuse.org/svn/yast/trunk/http-server/src/HttpServerWidgets.ycp Have a nice day Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- Ano, ano. Moudry rozkaz. Sam jsem nemel v tech gratulacich jasno.

1 0

[yast-devel] Builtins and Namespaces
by Arvin Schnell 13 Jun '08

13 Jun '08

Hi, we have found a way to add builtins to YCP in namespaces (found is correct since everything was already available). Just as a prove of concept I have added some mathematics functions in the namespace float I will likely need for advanced rounding with defined precision. The functions are abs, floor, ceil, trunc, pow. Caution: You do need a never version of yast2-devtools for generating the documentation. With the old version you get a make error. Otherwise there are no incompatibilities, neither on bytecode or library level. ciao Arvin -- 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] DnsServerAPI.pm
by Michal Zugec 13 Jun '08

13 Jun '08

Hi! Because of dependencies I moved $SUBJ from yast2-dns-server into yast2 package. This was because of bnc#392606 (yast-http-server dependency), but if any other packages are affected, please fix them. All changes are in svn trunk, packages are not in autobuild yet. Bye, Michal -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

8 15

[yast-devel] introduce a package history to remove obsolete packages
by Hanno Svoboda 11 Jun '08

11 Jun '08

I use yast in openSUSE 10.3 to manage my software packages. I like to explore many different FLOSS projects and install quite a lot of software which I remove later on. A big problem for me is that my installation becomes more bloated after a while, because libraries and dependencies which came with the installed software can't be identified and are not automatically removed (probably for a good reason). Therefor I like to propose an idea, which could potentially solve this issue: 1. Create a history of installed packages with following information: When Package X was installed, also packages Y + Z were installed 2 If the user removes X, Y, or Z, YAST should asks: Should the other two packages (X, Y and/or Z) also be removed as they have no other dependencies? 3. If the user decides not to remove them or they have dependencies on W from a different installation time point, they should be tagged as potentially obsolete. 4. Removal of W should trigger again: Should Y and Z also be removed as they have no other dependencies and were marked as potentially obsolete? 5. If further dependencies exist or the user decides to keep them, Continue at 3. Either the loop ends in package removal or at stable state 3. I hope this is not too confusing and this package bloating issue can be tackled. I am happy to clarify or maybe somebody else has a better (simpler) idea. If you think that sort of makes sense, you can read on some refinements below. Hanno PS: Unfortunately, I cannot program and can't produce any poof of principle implementation. I think their is no big logical error in it, but I am sure it needs some polishing here and there. ----------------- REFINEMENTS to the idea above, which make it more complicated and powerful. Points 2, 4 and 5 remain as they are. 1. Make a history of installed packages, which hold following information: When Package X was installed, also packages Y + Z were installed which are in an dependency relation to X. If the dependency criterion is not used, unrelated software that was installed at the same time (e.g. two completely unrelated programs) would fall under the removal category, which is unwanted. 3. If the user decides not to remove them they should be tagged as potentially "obsolete without dependencies". If they have dependencies on W from a different installation time point, they should be marked as "obsolete with dependencies". The user could use an option in YAST to remove all obsolete packages in the installation which are tagged "obsolete without dependencies". -- 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] Re: [opensuse-packaging] [Announcement] Ports for SuSEfirewall added via packages
by Lukas Ocilka 11 Jun '08

11 Jun '08

Michal Marek wrote: > Lukas Ocilka wrote: >> Hi, >> >> I'd like to announce one major change in openSUSE 11.1 / SLE 11: > ... >> This statically-defined library has been obsoleted by feature "Service >> Definitions Added via Packages" since openSUSE 10.3, openSUSE 11.0 still >> contains these definitions but some have been already replaced with the >> new dynamically-defined services. > ... >> Please, make sure your packages provide service definitions for >> SuSEfirewall2. See also: >> http://en.opensuse.org/SuSEfirewall2/Service_Definitions_Added_via_Packages > > AFAICS this page describes the behavior added in 10.3. So what exactly > will be changed in 11.1? There will be no hard-coded services in SuSEFirewallServices YaST library anymore. Everything must be dynamically loaded otherwise YaST Firewall will ignore these open ports and show them only in "Advanced Configuration" as an unnamed set of allowed ports. In openSUSE 11.0, you can still open YaST Firewall and see "Samba Server" in services to allow without having samba-server installed. But YaST Firewall can not be responsible for defining ports that should be open for a particular service, instead that package/er is responsible. Bye L.

1 0

Re: [yast-devel] HAL vs hwinfo
by Klaus Kaempf 11 Jun '08

11 Jun '08

* Danny Kukawka <dkukawka(a)suse.de> [Jun 11. 2008 00:01]: > > Please note: DeviceKit is atm ready for nothing. I don't think that we can or > should switch away from HAL for CODE11. > > IMO DeviceKit need at least one year to get usable (never mind get stable (API > and in general) or replacing HAL with all the existing information and > functionality). Great, thanks for the information. One thing less to worry about :-) Klaus -- 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] Nuernberg YaST team - meeting 2008-06-10
by Duncan Mac-Vicar Prett 10 Jun '08

10 Jun '08

Nuernberg YaST team - meeting 2008-06-10 minutes: dmacvicar * opensuse-updater-kde (now kupdateapplet) is being refactored (tgoettlicher) * work on partitioner redesign will continue after 11.0 GM. (aschnell) discussion over libstorage features for SLE11 and the ones needed for CIM providers. * ncurses yast UI plugin is getting also a review and cleanup (sh) * stefan will look into dumbtab widget. gaby will assist, and possibly ma too in need of help (feature #303491) * research on a common base dialog class for consistant button order (feature #303446) sh idea: keep button order in the base class, when modules use it, switch it to desktop dependant order, to avoid temporary inconsistencies. * jdsn working on SMT, will prepare enhancements for his packages in the build service. * libzypp will start getting commit part refactored (ma), who will coordinate also NU repo type support with the Prague team. * snwint and mantel: work on ipv6 stuff after GM. -- 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] User Interface Documentation - Lost or hidden? :)
by Lukas Ocilka 10 Jun '08

10 Jun '08

Hello, I'm just trying to build the YaST Overall documentation for openSUSE 11.0 but I've found out that because of splitting some parts into separate packages something is missing. Compare http://forgeftp.novell.com/yast/doc/SL10.3/tdg/Book-UIReference.html and http://forgeftp.novell.com/yast/doc/SL11.0/tdg/Book-UIReference.html 'UI builtin commands', 'Standard (mandatory) widgets', and 'Special (optional) widgets' are missing. Does anybody know where they are :)? How can I generate the documentation now? Thanks in advance Lukas

2 1

[yast-devel] HAL vs hwinfo
by Michal Zugec 10 Jun '08

10 Jun '08

There was discussion if we can use HAL instead of (or together with) hwinfo. So first, what is difference between informations that both of them provides. As an example I'll compare network card: hwinfo --netcard: 27: PCI 200.0: 0200 Ethernet controller [Created at pci.301] UDI: /org/freedesktop/Hal/devices/pci_8086_109a Unique ID: rBUF.m98l3Qk54R0 Parent ID: z8Q3.ZbAWgKMCoE3 SysFS ID: /devices/pci0000:00/0000:00:1c.0/0000:02:00.0 SysFS BusID: 0000:02:00.0 Hardware Class: network Model: "Lenovo ThinkPad T60" Vendor: pci 0x8086 "Intel Corporation" Device: pci 0x109a "82573L Gigabit Ethernet Controller" SubVendor: pci 0x17aa "Lenovo" SubDevice: pci 0x2001 "ThinkPad T60" Driver: "e1000" Driver Modules: "e1000" Device File: eth0 Memory Range: 0xee000000-0xee01ffff (rw,non-prefetchable) I/O Ports: 0x3000-0x3fff (rw) IRQ: 216 (8638 events) HW Address: 00:16:41:aa:74:56 Link detected: no Module Alias: "pci:v00008086d0000109Asv000017AAsd00002001bc02sc00i00" Driver Info #0: Driver Status: e1000 is active Driver Activation Cmd: "modprobe e1000" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #12 (PCI bridge) lshal: udi = '/org/freedesktop/Hal/devices/pci_8086_109a' info.bus = 'pci' (string) info.linux.driver = 'e1000' (string) info.parent = '/org/freedesktop/Hal/devices/pci_8086_27d0' (string) info.product = '82573L Gigabit Ethernet Controller' (string) info.subsystem = 'pci' (string) info.udi = '/org/freedesktop/Hal/devices/pci_8086_109a' (string) info.vendor = 'Intel Corporation' (string) linux.hotplug_type = 2 (0x2) (int) linux.subsystem = 'pci' (string) linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0' (string) pci.device_class = 2 (0x2) (int) pci.device_protocol = 0 (0x0) (int) pci.device_subclass = 0 (0x0) (int) pci.linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0' (string) pci.product = '82573L Gigabit Ethernet Controller' (string) pci.product_id = 4250 (0x109a) (int) pci.subsys_product = 'ThinkPad T60' (string) pci.subsys_product_id = 8193 (0x2001) (int) pci.subsys_vendor = 'Lenovo' (string) pci.subsys_vendor_id = 6058 (0x17aa) (int) pci.vendor = 'Intel Corporation' (string) pci.vendor_id = 32902 (0x8086) (int) As you can see some informations are missing in HAL : - sysfs - driver, link status - modaliases : available drivers But maybe we can split hwinfo into HAL and sysfs agent and modaliases agent, that should work. Steffent, would that works? Just to know - it's just a research of possibility ;-) Bye, Michal -- Best Regards, Michal Zugec Software developer --------------------------------------------------------------------- SuSE CR, s.r.o. e-mail: mzugec(a)suse.cz Lihovarska 1060/12 tel: +420 284 028 960 190 00 Praha 9 fax: +420 296 542 374 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

5 4