July 2007 - YaST Development - openSUSE Mailing Lists

[yast-devel] yast-kdump screen shots
by Maneesh Soni 09 Jul '07

09 Jul '07

Hi Jozef There are few more changes which I think would be good to have. Please let me know if these are possible to make or not. 1. Start-up ----------- Please move the "kdump memory" settings from "Dumping" screen to "Start up". As, IMHO, the start-up setting should have the minimum things which are absolutely necessary for enabling kdump service. Without reserving memory one cannot enable kdump. 2. Save Dump Image ----------------- IMHO, we can rename the tittle to something like "Dump Target Settings". The other options looks great. Only a couple of issues, firstly, in case of "Raw Disk", I think the "Directory for saving Dumps" is not needed. Secondly, for NFS, I think "Share" is not needed. 3. Expert Settings ------------------ IMHO, this tab should contain all the settings which normally user will not change. Apart from kdump kernel command like options, we can move the setting wrt "No. of Old Dumps" from "Dumping" screen to expert settings. Also can we put one more option to use a custom kdump kernel initrd which can be used save/process the dump. 4. Dump-filtering ----------------- I think we should either merge this with "Dump Target Settings" or if there is not much space left there, then a separate screen. Please let me know if these make sense or not. Regards Maneesh -- Maneesh Soni Linux Technology Center, IBM India Systems and Technology Lab, Bangalore, India -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

3 21

[yast-devel] Submitted libzypp-3.11.1 and yast2-qt-2.15.6 to BETA
by Michael Andres 09 Jul '07

09 Jul '07

yast2-qt-2.15.6 in BETA is ready to be tested. Esp. the former InstSource view - now 'repository'. -- 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

2 1

[yast-devel] Changing YaST Packages in Autobuild
by Lukas Ocilka 09 Jul '07

09 Jul '07

Hi, It happens time to time that someone needs to urgently change some YaST package in autobuild. This is actually possible but you should know that autobuild is not the primary source of YaST packages. Our primary source is our SVN: http://svn.opensuse.org/svn/yast/ First, you had better contact the MAINTAINER of the package and consult the change with him/her. You can change the package in autobuild but you need to send a diff file to the maintainer or change SVN as well. Please, NEVER submit a changed package to autobuild without announcing the change to the maintainer of the package and without providing the patch or changing the source directly in SVN. Thanks & Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic

1 0

[yast-devel] Submitting libzypp-3.11.0 to BETA
by Michael Andres 05 Jul '07

05 Jul '07

- Package::location is now returns an OnMediaLocation - ResObject::archivesize() renamed to downloadSize() At least the above requires changes to zypper, kg-bindings and the UIs. - Allow to iterate all Repositories that contribute Resolvables to the Pool. - MediaSetAccess::provideDir added - remove useless url check - add old-api-style wrapper - Add MediaProducts class - revision 5892 - version 3.11.0 -- 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] [RFC] QueryBuilder and (Resolvable)Query
by Jan Kupec 05 Jul '07

05 Jul '07

Hi! Here is my proposal of a new libzypp API for various metadata queries. It should be useful for YaST package managers, zypper, YaST online update and maybe others. Pease see attached QueryBuilder.h file and comment on the design and usability. QueryBuilder is meant to build an sqlite query for libzypp's metadata cache database and to be used by ResolvableQuery::query(QueryBuilder,ProcessingFunctor) function (or other Query class) to do complex resolvable data queries. Result of these queries will be processed by ProcessingFunctor (read on). The reason to create such an API is to have a convenient API for coding various kinds of user queries, so that apps using libzypp don't have to code the functionality by themselves by traversing the resolvable pool. And since we (will hopefully) have the new metadata cache database, there is another reason: to make use of the database to speed up the search and save memory requirements (don't load the pool, just query the database). I would have to code it once in zypper anyway, so this way it can be reused by others as well. CODE EXAMPLE: //////// code START ///////////////////////////////////////// bool is_regexp; // treat the search string as regexp? bool search_summaries; // search also in summaries? string search_string; // user given search string Resolvable::Kind kind; // the result will be limited to this kind <snip> zypp::cache::QueryBuilder builder; builder.addName(search_string, is_regexp); if (search_summaries) builder.addAttribute(zypp::cache::attrResObjectSummary(), search_string, is_regexp); builder.addKind(kind); zypp::cache::ResolvableQuery resquery; resquery.query(builder, processing_functor); //////// code END ///////////////////////////////////////// (the functor is function<bool( const data::RecordId &, data::ResObject_Ptr )> we can provide one which would use Selectables (or NameKindProxy) for yast as well) FEATURES - search by name, any cache attribute, kind, (future: installed status), version - uses simple strings or regexes - search by dependencies (select resolvables which are required by e.g. pattern X) - use multiple search conditions and choose to require all or any of them satisfied. IMPLEMENTATION - based on given arguments and options, an sqlite command will be built This command will be executed by a ResolvableQuery::query() or another Query class (see attachment - just a stub). - i decided to write field values into the sqlite command string itself. Using variable names and bind values to them would be too complex. - regexes - sqlite's REGEXP keyword will be used, bound to user (libzypp) defined regexp matching function of our liking. ISSUES - what regexp syntax do we want to support? - something missing/to be changed in the API? Cheers, Jano

5 9

[yast-devel] Changeset 39159 adds XML representation to YCP
by Klaus Kaempf 05 Jul '07

05 Jul '07

As part of hackweek project http://idea.opensuse.org/content/ideas/ycp-to-ruby-translator I just committed changeset #39159 to yast-core on svn trunk. This changeset adds toXml() methods to all YCP and YCode classes, giving all ycp code and data structures a representation as XML. Klaus --- SUSE LINUX Products GmbH, 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

3 6

[yast-devel] pkg-bindings in BETA - status
by Ladislav Slezak 04 Jul '07

04 Jul '07

Hi all, I just have submitted yast2-pkg-bindings to BETA. Many bindings have partial or empty implementation and it's completely untested. But it at least compiles and we should be able to see really failing packages in BETA (the failures which are not caused by dependency to pkg-bindings). It needs the latest libzypp from SVN, it might be still failing in autobuild until libzypp is submitted. If anybody is interested in fixing/improving pkg-bindings just check it out from http://svn.opensuse.org/svn/yast/branches/REFACTORING-10_3/pkg-bindings/ Look for '#warning', 'TODO' and 'FIXME' strings for missing functionality. (BTW I'll be out of office until the next Monday.) Ladislav -- 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] Regarding "Installation source" vs "Repository"
by Andreas Jaeger 04 Jul '07

04 Jul '07

Hi Guys, there have been quite some discussions regarding the terms "Installation Source", "Repository" and "Catalogs". Product Management had decided that for SLES10 and SLED10 - and products based on that the term "Catalogs" is to be used. We want to use the same name in all cases and therefore consider changing it for our products and this involves some discussions. There was no management decision at all to use "Catalog" for future products, Rebecca seems to have misunderstood something. As you've noticed, there's some confusion on how to move forward. I'm travelling right now and will continue this discussion to get everybody - both you as community and us Novell folks - aligned on this. I'm sorry for how this currently pops up and I'm not happy about it. Regards, Andreas P.S. As I'm travelling I haven't had time to read the complete discussion. Please bear with me - I might not be online before tuesday again. -- Andreas Jaeger, aj(a)suse.de, http://www.suse.de/~aj/ SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126

1 2

[yast-devel] Wizard dialogs without help?
by Johannes Meixner 03 Jul '07

03 Jul '07

Hello, for HackWeek I am working on an experimental YaST module, see http://idea.opensuse.org/content/ideas/usable-printer-setup-tool Currently I use for the dialogs something like -------------------------------------------------------------- Wizard::SetContentsButtons ( caption, contents, HELPS["basic_add_dialog"]:"", Label::BackButton(), Label::NextButton() ); -------------------------------------------------------------- Is it possible to get Wizard dialogs without help sub-window? I.e. have full-screen contents? Reason 1: My superb new innovative dialogs (TM) are fully self-explanatory so that there is no need for any help text at all. Reason 2: I read in books from usability experts that a UI is very likely bad designed when explanation texts (aka. help texts) are needed. Reason 3: My superb new innovative dialogs (TM) are perfectly designed ;-) 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

9 21