June 2007 - YaST Development - openSUSE Mailing Lists

[yast-devel] shell menu generation
by Scott Reeves 11 Jul '07

11 Jul '07

GNOME uses the freedesktop menu and .desktop spec standards to generate all it's menus - the traditional menu, the application browser and the control center. This method uses a .menu file and the Category= line from .desktop files to determine which menu entry a .desktop file falls into. AFAIK KDE also uses this for it's main top level menu. As of sp1 we added the yast2 control center which also uses this method. I was not involved in the very start of this so I don't want to speak incorrectly but I think a .menu file was generated that simply contained all the menu categories that currently showed in the qt shell. Then it used the already existing Categories= lines in .desktop files like /usr/share/applications/YaST2/users.desktop Unfortunately, that means there is currently two ways to generate the yast2 menus - the yast2 specific way using the X-SuSE-YaST-Group key and the Category= way. Towards the end of SP1 we ran into some issues with this. Using the .menu/.desktop specs to generate the menus means we get common code shared between all the menus and we can use the standard gmenu library to parse all the relevant information from the .desktop files including supporting all the other tags such as OnlyShowIn, Hidden, ... Could we move to supporting the .menu/.desktop spec way of generating menus for the yast shells – given that almost all of the existing .desktop files contain some sort of “Categories=X-SuSE-YaST-*” line it appears something along that lines is already under way. -- 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] 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] [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] 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

[yast-devel] Adding missing API to libzypp (or between libzypp and apps)
by Jan Kupec 29 Jun '07

29 Jun '07

Hi there! Check out this idea page and see what's needed and who intends to do what: http://idea.opensuse.org/content/ideas/better-api-for-applications-using-li… This idea might be of interest for people writing applications using libzypp who were missing some functionalities and libzypp devels. In particular: YaST package manager UI (qt, gtk, curses), zypper, YaST online update. If you have any comments or want to participate, edit that page and use the discussion facility there and describe what would you like to do. Jano -- 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] Redefinition of WizardStepsDialog
by Lukas Ocilka 28 Jun '07

28 Jun '07

Hi, For a Game Add-On during installation I'd (lmichnovic wants me to do it :)) like to redefine the "Help" button label and handling. The goal would be to have a "Game"-labeled button with a callback function assigned to handle it. Is there some possibility? UI::WizardCommand? Where can I find some documentation, please? Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic

1 0

[yast-devel] hackweek, ruby support for yast progress
by Duncan Mac-Vicar 26 Jun '07

26 Jun '07

you can read it here: http://duncan.mac-vicar.com/blog/archives/245 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

1 0

[yast-devel] New UI Widget -- Idea for Qt and GTK+ interfaces
by Lukas Ocilka 22 Jun '07

22 Jun '07

Hi, When YaST developer or designer are designing the YaST dialogs, they need to define some relative sizes between widgets. Unfortunately, the worst cases cannot be expected and we usually ignore them. Please, see the attachment in this mail. The 'Repository Description' is always replaced with a new one when some other repository is selected in the 'List of Repositories'. The worst case is that there fifty repositories in the 'List of Repositories' but most of the descriptions need thirty lines in the 'Repository Description'. Please, don't write that it would be a _wrong description_, such cases just happen time to time. My idea of a solution would be a user-controllable slider in UI - a new widget for graphical UI. Users could then themselves decide what is more important for them if the data don't fit the UI because screen is not inflatable ;) I'd like to ask YaST developers whether they feel this is worth a feature request and whether it makes even sense to want it. I know that both Qt and GTK+ could implement it but I don't have any idea how difficult would it be. Please, before writing "wrong UI design", "wrong data" ... think about that a few seconds :) If you always wanted such UI feature, write it too ;) Rather think about the advantages of it first :) Thanks & Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic

18 57

[yast-devel] Modified changelogs in YaST packages
by Lukas Ocilka 22 Jun '07

22 Jun '07

Hi, It seems that several YaST packages might have been changed just in the autobuild / build service. Please, merge those changes into your packages in trunk. For more information, please, read the attached mail. 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] Re: [zypp-devel] Source refresh policy
by Jan Kupec 21 Jun '07

21 Jun '07

(Posting also to sw-management and yast, as this is (most of it) not zypp-specific. Please, discuss parts which are not zypp-specific on sw-management <opensuse-softwaremgmt(a)opensuse.org>.) Jiri Srain wrote: > Hi! > > This is my suggestion on how to define the refresh policy with refactored > ZYPP: > > We need to keep the information when last a source was refreshed in order > to decide whether a source needs to be refreshed or not. In addition, we > will need some policies defining whether a source should be refreshed or > not. > The basic refresh should be done by a cron job. However, there may be > a reason not to do refresh via a cron job and do it only when SW management > tool starts. (if you don't have much time to read all this, skip to the IMPORTANT part below) I personally don't like either of these ideas: 1) If doing refresh in cronjob, the user can get surprisingly stuck when trying to use zypp in the very moment when the repos are being refreshed. Also the huge download happens without user's supervision. However, we can offer the user to set up the cron job for him, but we cannot do it behind his back. Or he can set up a cron job by himself. 2) Please NOT when a SW management tool starts!! This is much more annoying than getting a "repository out-of-date" warning! Let's leave it to the user when he wants to refresh. E.g., often user just wants to quickly check whether a package is in the repository and doesn't need an up-to-date data. At least, ask him at the tool start-up, and only if the refresh is needed (current repomanager is able to check whether a refresh is needed, Duncan do we have a simple method for the check, or is it hidden in the code? something like RepoManager::isUpToDate(RepoInfo) would be nice). What i said above does not hold true for every SW management tool. For example, updater applets should always have up-to-date data (as Jiri says a few lines below). IMPORTANT: always respect autorefresh setting! ...on the second thought... :O) We have this _autorefresh_ setting in .repo file which can be enabled/disabled for each repository separately by the user. If we respect this setting, then forget what i said above and i'll be fine with crons and on-start refreshing :O) behavior clarification: - autorefresh disabled - refresh metadata ONLY ON USER REQUEST (e.g. zypper refresh, (new) Refresh button in YaST). - autorefresh enabled - application chooses when to refresh We should just think about whether to enable or disable it by default. Example use case: for online update repo (small repo with patches) i'd use autorefresh enabled and let whatever app needs it to refresh it as it sees fit. But for factory i want to be in complete control when it will be refreshed (because of the amount of resources it takes - time, CPU, network), so i'd use autorefresh disabled. BTW: for cronjobs i'd recommend something like zypper refresh --respect-autorefresh (not implemented yet :O) because otherwise it would try to refresh all sources. (Also there will be zypper refresh --force to force refresh even if zypp indicates that it is not needed, but that's just by the way...) > There are two kinds of tools: > 1. Tools which take care of having the system up-to-date. They must always > work on as fresh metadata as possible > 2. Tools which should install a package. They should work as fast as possible. > we can pay the price of installing package which already has an update at > least in some cases. > > Therefore we need two different policies depending on the kind of source > (this is optional) and on the operation user performs (they can be set > to vehave the same of course). > > How often refresh is being performed via cron (if it is) can be read from > the cron configuration, I don't think we need to put this information to > any configuration file. > > In addition to cron, I suggest adding following variables (comments hopefully > explain their meaning) > > > --- snip --- > > # should the on-line update paplication (eg. YOU) consider doing a refresh > # or should it rely on a cron job? > ONLINE_UPDATE_AUTO_REFRESH="yes" > > # if the time since last refresh is higher than specified amount of time, > # the update tools refresh the source first > # if it is an update source (provided we have the tags); 0 means to refresh > # always when starting the on-line update tool > # filtering on-line update sources is questionable (consistency) > ONLINE_UPDATE_REFRESH_INTERVAL="1h" > > # should the desktop applet perform any refresh or just rely on cron job? > DESKTOP_APPLET_REFRESH="yes" > > # define how often the desktop applet should perform refresh. > DESKTOP_APPLET_REFRESH_INTERVAL="3h" > > # master switch for enabling or disabling auto refresh for software > # management tools (eg. 'yast -i', 'zypper') > # if disabled, refresh must be performed manually or via cron > INSTALLER_AUTO_REFRESH="yes" > > # auto refresh interval for tools primarily installing packages, not doing > # update; "0" means always when initializing source(s) > INSTALLER_AUTO_REFRESH_INTERVAL="24h" > > --- snap --- > > The above variables can be added to /etc/sysconfig/sw_management. > > The way time is specified can be discussed, I guess that the granularity of > hours or at most minutes is perfectly sufficient, however, we may support > any of fixed units or specifying the units with the value (as in examples > above). > Cheers, Jano -- 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] Re: [yast-announce] yast2-gtk now imported to the YaST repository on svn.opensuse.org
by Ricardo Cruz 20 Jun '07

20 Jun '07

Ter, 2007-06-19 às 17:12 +0200, Jiri Srain escreveu: > Hi! > > The Gtk UI frontend for YaST has been imported to the YaST subversion and is > now available at > > http://svn.opensuse.org/svn/yast/trunk/gtk/ > Thanks Jiri! I have synced stuff done in the meanwhile, and instructions to do a checkout were posted in our wiki page: http://en.opensuse.org/YaST2-GTK Cheers, Ricardo > Please, work on this repository instead of the one on svnforge.novell.com. > > According to the Changelog file, the last change is following: > > 2007-05-23 Ricardo Cruz <rpmcruz(a)alunos.dcc.fc.up.pt> > > * src/ygtkwizard.c: changed title alignment. > > * src/ygtkfindentry.c: overload entry's context menu key binding > by our own, if set (see package selector). > > * src/YGUI.cc: ignore widgets without YGWidget representation > (ie. YWizard buttons wrappers). > > If you did any changes since then, make sure that they are also at > svn.opensuse.org and if needed, recommit them there. > > Thanks! > > Jiri > -- 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] Re: [zypp-devel] ZYPP: TRUNK->BETA REFACTORING-BACKUP-10_3->STABLE
by Jiri Srain 20 Jun '07

20 Jun '07

Dne středa 20 červen 2007 13:31 Michael Andres napsal(a): > svn copy -r 5789 > http://svn.opensuse.org/svn/zypp/trunk/ > http://svn.opensuse.org/svn/zypp/branches/REFACTORING-BACKUP-10_3 > > > REFACTORING-BACKUP-10_3 is a snapshot of the latest libzypp revision > we comitted to STABLE. > > TRUNK is now submitted to BETA only, until all the outdated Source* > stuff is removed, an all applications switched to the new Repo* > classes. > > > How to handle it in YaST? In the past, we created a temporayr branch for the new stuff and kept submitting trunk to STABLE (so that it was consistent in the whole repository). Any reason why not to do it this way? Jiri > > > -- > > 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 > +------------------------------------------------------------------+ -- 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

2 2

Re: [yast-devel] Fwd: YaST font different from KDE apps?
by Martin Vidner 19 Jun '07

19 Jun '07

On Mon, Jun 18, 2007 at 10:57:05PM +1000, Mohammad Bhuyan wrote: > Hi Martin, > > My apologies to email you direct as many attempts to pass the image to > fails. The image is now attacked with this email. > > My original question: > > But then why the original fonts with default installation (with MS > fonts) were same everywhere (KDE & YaST). Once changed to Liberation > fonts in KDE, KDE apps shows Liberation fonts where YaSt shows the one > which I am trying to know what font that is? I have uploaded the image to http://en.opensuse.org/Image:YaST_or_desktop_font.jpg (but I don't know the answer to your question. Anyone?) -- 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

4 3

[yast-devel] Fwd: YaST font different from KDE apps?
by Mohammad Bhuyan 18 Jun '07

18 Jun '07

Hi, Sent the following email to opensuse list. Due to the image size couldn't send the email to this list. Regards, Mohammad ---------- Forwarded message ---------- From: Mohammad Bhuyan <nuxser(a)gmail.com> Date: Jun 16, 2007 4:08 PM Subject: YaST font different from KDE apps? To: SuSE Linux <opensuse(a)opensuse.org>, yast-devel(a)opensuse.org Hi, I am using Liberation fonts with Liberation Sans being my KDE desktop font. Quite happy with how its looks (even better with subpixel hinting) but noticed an issue with YaST. Fonts in YaST seems to be little different from the other apps. I need second (third, forth, more the marrier) opinion if it is indeed a different font or not. I have attached a snapshot. And if it is a different font then its a bug in Yast to ignore fonts imposed by kde configuration. Thanks, Mohammad -- 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] YaST goes yellow-black :-)
by Katarina Machalkova 18 Jun '07

18 Jun '07

Hola! I've created new theme for text-mode YaST interface, so besides default white-on-blue one, you can now enjoy yellow-on-black theme, which will be applied in the future to urxvt-style terminals by default. Here are some preliminary screenshots: main window: http://users.suse.cz/~kmachalkova/mainwin.png sw_single module: http://users.suse.cz/~kmachalkova/swsingle.png release notes (richtext): http://users.suse.cz/~kmachalkova/relnotes.png Once feature #301893 is finished, you can pick text-mode YaST interface theme yourself by defining sysconfig variable Enjoy! B. -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter

6 9

[yast-devel] How to display license agreement when using autoyast
by Harry Hart 15 Jun '07

15 Jun '07

Hello - Please forgive the very basic question, but I'm hoping someone can suggest a solution. How can I arrange for a license agreement to be displayed during an autoyast install? I have tried the following possibilities, but so far, none seems to work: 1. Turned on <confirm>true</confirm> in the autoyast XML control file. 2. Added a "workflow" and "module" element in the autoyast control file. 3. Added a license.zip file to one of the "add-on products" (This works when adding the "add-on" after installation, but not during auto-install.) 4. Added the yast2-firstboot package to the list of packages to be installed. If I understood how autoyast determines which YCP modules to run (and in what order), then I could try adding my own (to the "root" CRAMFS archive on the installation medium), but so far, I don't understand how to tell autoyast to run an additional new module. (I am using SLES 10, not OpenSUSE.) Any help, pointers, explanation would be much appreciated. Thanks in advance! - Harry -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

2 2

[yast-devel] [PROPOSAL] adaptation of zypp apps to new repo management API
by Jan Kupec 15 Jun '07

15 Jun '07

Yesterday we (Prague YaST team) had a discussion about how to proceed with adaptation of YaST to the new repository management API of libzypp. First thing to note, the API has yet to mature in the upcoming days, as we test it with zypper and still modify it as needed. _After_ the API is declared done, we propose to proceed as follows: 1. document transition from old API to the new one (a method to method, code to code map) and post to yast-devel. 2. drop the old source management code from libzypp trunk 3. submit libzypp trunk package to BETA (all dependent packages will then fail building and maintainers will get the notice). 4. maintainers of the dependencies adapt their code 5. after tuning, submit all the stuff to STABLE (in time for the last Aplha release) If you are a maintainer of a package affected by the changes in libzypp, please provide feedback on the new API as you start looking at it (probably after publishing the transition document). Cheers, jano -- 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] YCP return bug?
by Benji Weber 12 Jun '07

12 Jun '07

Hi all, Could someone tell me whether this is a bug in YCP or if I am misunderstanding the documentation, it is certainly counter-intuitive. The documentation (http://forgeftp.novell.com//yast/doc/SL10.2/tdg/id_ycp_return.html) states: The return statement immediately leaves the current function or a current top level block (that contains it) and optionally assigns a return_value to this block. If blocks are nested, i.e. if the current block is contained in another block, the return statement leaves all nested blocks and defines the value of the outermost block. Therefore I would expect the following programme to print "One" "Two" "Three". However, it actually prints "One" "One" "Three". { string One() { return "One"; } string Two() { string value = "One"; foreach(string str, ["Two"], { return str; }); return value; } string Three() { string value = "One"; foreach(string str, ["Three"], { value = str; }); return value; } y2milestone(One()); y2milestone(Two()); y2milestone(Three()); } _ Benjamin Weber -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

5 7

[yast-devel] [Bruno Haible] Re: xgettext: Extracting comment blocks from YCP files
by Karl Eichwalder 12 Jun '07

12 Jun '07

Please, change comments in YCP source files as explained in the attachment, if time permits. This bug surfaced along with https://bugzilla.novell.com/show_bug.cgi?id=230388 aTdHvAaNnKcSe! Karl -- Karl Eichwalder R&D / Documentation SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg)

2 1

[yast-devel] y2makepot
by Ken Millett 12 Jun '07

12 Jun '07

y2makepot is using all of my src files except for my helps.ycp file. Is it supposed to include helps.hcp? I think it used to, but I'm not sure. -- 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] changes in yast2 lan
by Michal Zugec 07 Jun '07

07 Jun '07

Hi all, I want to make some changes with internal data structures in lan module (maybe later in other modules). Status now: - there are about 4 lists/maps (hwinfo, network configuration, hwcfg configuration, table items description) + some informations read from /sys filesystem - there are more places when these items are "matched" and there was some bugs that sometimes with different results ;-) Idea: - create one list of maps and match them just once - also I want to put there information from udev rules Example: list<map> lan_configuration = [ $[ "id":0, "hwcfg" : ... "ifcfg" : ... "hwinfo" : ... "table_descr" : ... "udev" : ... ], $[ "id":1, ... ] ] Not detected devices will have "nil" for hwcfg and not configured will have nil for ifcfg ... What do you think? 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

4 5

[yast-devel] Fw: Fwd: Mockups pre kdump
by Maneesh Soni 05 Jun '07

05 Jun '07

Hi Bernhard, We have the following observations & suggestions about the mock-up screenshots. Sorry about the long mail and taking some time in replying. We would also like to suggest changes in the kdump user scripts (kdump initrd) and based on that the yast kdump configuration screens will need changes. ************************************************************** 1) General Settings =================== We liked the three way enable/disable settings and they are at the right place, but the other portions like kernel command line or kdump commandline should be part of the expert settings as generally user should be provided with default set of kernel command line options and rarely one has to change them. Instead of command line settings, it would be useful to have the setting related to reserving memory for kdump kernel. The tool can have display like ---------------------------------------------------------------------------- Total system Memory (MB): 4096 (just informative) kdump Memory (MB): (A list box with a minimum memory value like 128, and option to increase should be there) Usable Memory (MB): 3968 (this is also informative) ---------------------------------------------------------------------------- 2) Dump Settings ================ This should capture the settings about dump target and other misc settings about daump saving. Apart from this, "the dump filtering" options for the "makedumpfile" utility can also be integrated here. So, Dump Target ----------- (a radio button to select either of the three targets like o Local filesystem - here we can have a list box with list of valid disk partitions with supported filesystems - path location o Network - This is for possible future extention of dump saving mechanism using which we can save the dump over network ie over NFS or scp, through the kdump initrd. For this we will need following settings - a radio button for selecting NFS or SCP - IP address of the server - path (exported path for NFS or target path for scp) o Raw disk - here we can have list of available paritions without any filesystem on them Default dump path (ie relative to the dump target) ----------------- [ /var/log/dump ] (select directory button) Dump filtering options ----------------------- - This should capture settings for options for using the dump fitering tool "makedumpfile". I am not sure right now if we need a separte screen for this or "Dump settings" is ok. 3) Expert Settings ================== - kdump kenrel command line options [ ] - path to custom kdump kernel [ /boot/vmlinuz-my-kdump-kernel ] - path to custom kdump kernel initrd [ /boot/initrd-my-kdump.img ] - Note: The current approach is to provide user a distro built kdump kernel. But some users would like to use their own kernel to minimize the reserve memory requirement. Also. the kdump initrd might be different if the user is trying to save dump thruough initrd in soe unsual envirnment like multipath IO etc. ************************************************************************* These might be confusing but please let me know if I can elaborate more. The kdump initrd related changes I was taking about are probably not the right stuff for this mailing list but please bear it here.. so that we can have the right context for discussions 1. The current approach in of using a _dedicated_ disk partition somewhat defeats the purpose of kdump flexibility. This mandates that use has to have a separte disk parition allocated just for kdump. The alternative is to have initrd based solution. In past we have done a prototype for such approach http://lse.sf.net/kdump/patches/automation/sles9-sp2-mkinitrd-1.2-27.9-auto… Here using initrd we copy the dump directly to the disk filesystem and avoid the intermediate step of copying to a raw partition and then to target path. This approach does make initrd somewhat bigger in size but it doesn't need user to have a dedicated disk partition just for kdump. 2. As of now there is no support for saving the dump over network using NFS or scp. The network dump can also be done using the kdump initrd once the user has specified right config parameters. So, overall kdump initrd should be able to copy the dump to all possible targets depending upon the user settings. 3. As of now the dump filtering tool is not integrated with kdump user scripts so we can get that also integrated in the initrd and have smaller size dumps based on options given to "makedumpfile" tool. Thanks Maneesh ----- Forwarded message from Bernhard Walle <bwalle(a)novell.com> ----- Date: Thu, 12 Apr 2007 00:32:22 +0200 From: Bernhard Walle <bwalle(a)novell.com> To: Maneesh Soni <maneesh(a)in.ibm.com> Cc: tiwai(a)suse.de Subject: Fwd: Mockups pre kdump Hello, as you may remember you wanted some discussion about the new kdump YaST module. Here I got some early screenshots. I think we should continue the discussion about on the yast-devel(a)opensuse.org mailing list. See http://en.opensuse.org/Communicate how to subscribe. Thanks, Bernhard -- SUSE LINUX Products GmbH Tel. +49 (911) 74053-0 Maxfeldstr. 5 GF: Markus Rex 90409 Nürnberg, Germany HRB 16746 (AG Nürnberg) OpenPGP DDAF6454: F61F 34CC 09CA FB82 C9F6 BA4B 8865 3696 DDAF 6454 From: Jiri Srain <jsrain(a)suse.cz> To: bwalle(a)novell.com, tiwai(a)novell.com Subject: Mockups pre kdump Date: Wed, 11 Apr 2007 15:23:41 +0200 Hi Bernard and Takashi! I already have some mockups for the YaST dialogs for kdump, find them attached to this mail. I hope that the desired functionality of the module is obvious form them, even though some of the widgets may need better labels. Please, comment on them, also feel free to forward them to IBM. Jiri BTW: How should the module be called? Is yast2-kdump OK with you? -- 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 ----- End forwarded message ----- -- Maneesh Soni Linux Technology Center, IBM India Systems and Technology Lab, Bangalore, India

6 9

[yast-devel] installation & network
by Michal Zugec 04 Jun '07

04 Jun '07

Hi, I made some changes in network code for installation to make it easy to understand, no duplicate code, easy to debug, etc. I will document that changes in opensuse wiki (changes, current status and my plan to future) but not now and not here (after test that everything is ok). Here I want to describe package/file/root_file changes: ------------------------------------------------------------------------ yast2-installation: control/control.openSUSE.xml, control/control.xml - removed item "inst_netsetup", this file is removed from yast2-network network_finish.ycp, S07-medium - changes yast2-network : inst_netsetup.ycp - removed install.ycp - renamed to "save_network.ycp" this file should replace create_interface bash script NetworkStorage.ycp, Lan.ycp - changes inst-sys (root): - remove create_interface script - use save_network.ycp and NetworkStorage.ycp script in inst_sys - use changed control.xml (I hope that changes in svn are enought) ------------------------------------------------------------------------ Steffen, could you made that changes for inst-sys? I don't know if I should mark that files (and how)? yast2-network is not included in inst-sys, because is used for second stage, not first. But because of maintenance I would like to have that files in my package. Lukas - is that enough when I changed 2 xml files above, or do I need anythink else? Christian - all changes we talked before I will implement after this Thomas, Arvin, Uwe - I didn't checked autoinstallation because Storage is broken in autoyast (is it known bug or should I report this)? All changes are in subversion now, I will send them to autobuild probably after Tuesday's meeting and after your responses. 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

4 5