July 2007 - YaST Development - openSUSE Mailing Lists

[yast-devel] Re: [opensuse-fr] Re: [opensuse-doc] How to name that thing? Repository/installation source/Catalog...
by Pascal Bleser 23 Jul '07

23 Jul '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 jdd wrote: > Andreas Jaeger wrote: >> The decision was to use "repository". Other names considered where >> "installation source" and "catalog". > > could you also ask your translation team to give the official translation. > > At least in french, repository is not easy to translate. The very same > word exists but is completely obsolete (repositoire - meaning the place > where you store dead human corpse to family last visit :-()). > > http://fr.opensuse.org/Glossaire_d'équivalences_entre_l'anglais_et_le_français > > the best word seems to be "dépôt", but "Réserve" may be better. Package > repository gives "Réserve de paquetages", "Dépôt de paquetages" > (paquetage is very odd in french, but most used anyway) "Dépôt" is the adequate term IMO. - -- -o) Pascal Bleser http://linux01.gwdg.de/~pbleser/ /\\ <pascal.bleser(a)skynet.be> <guru(a)unixtech.be> _\_v The more things change, the more they stay insane. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org iD8DBQFGpH0fr3NMWliFcXcRAtiqAKCeXZpW5YE1eKXH7AP25iSHPQPkmQCfdNw6 XHLcxkTxklZMJoFCmtIhyAk= =raN+ -----END PGP SIGNATURE----- -- 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 repository filter in YaST ncurses - request for testing ;-)
by Katarina Machalkova 19 Jul '07

19 Jul '07

Hello! I've added a new feature to YaST ncurses UI - a list of all available repositories + related filtering of packages according to which repository they belong to. You may know this filter well from Qt UI, in ncurses it's brand new. Since no 'class recycling' could be used ;-) (I've written entirely new class for the filter from scratch) and since new zypp repository handling code has been used (and I'm not a zypp developer), I'd like to ask you for trying and testing this feature. If you do so, please report any segfaults ;-) missing repository information, even ugly dialog layout to me (in Bugzilla, assign to kmachalkova). The first one reporting a bug will receive a beer (or a chocolate, if (s)he prefers that) ;-) How to test: just install new yast2-ncurses 2.15.21and go to Filter->Repositories Thanks frozenB. P.S. Code review is also welcome, the whole thing is pretty well commented and documented -- \\\\\ Katarina Machalkova \\\\\\\__o YaST developer __\\\\\\\'/_ & hedgehog painter -- 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: [yast-announce] First translation round starts this week
by Jiri Srain 19 Jul '07

19 Jul '07

Hi! Since we change the terminology of the installation sources/catalogs, please, try to adapt at least some of the texts ASAP. Find the result of grep through the .pot-files atatched to this mail (probably not complete :-( ). I will generate the .pot-files for first translation round in a few hours. Thanks! Jiri Dne úterý 17 červenec 2007 09:18 Jiri Srain napsal(a): > Hi! > > The first translation round is starting this week. I will generate > the .pot-files for translators this week on Thursday afternoon. Please, get > as many new texts as possible to the subversion repository by Thursday noon > CEST. > > Thanks! > > Jiri -- 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

[yast-devel] Re: [yast-commit] r39517 - in /trunk/gtk: ChangeLog po/ po/pt.po src/YGPackageSelector.cc
by Jiri Srain 19 Jul '07

19 Jul '07

Hi Ricardo! Dne čtvrtek 19 červenec 2007 06:27 jste napsal(a): > Author: rpmcruz > Date: Thu Jul 19 06:27:59 2007 > New Revision: 39517 > > URL: http://svn.opensuse.org/viewcvs/yast?rev=39517&view=rev > Log: > * src/YGPackageSelector.cc: Jiri has added gettext support (not sure > if it is completed as I don't see the place for PO files and the rules > to compile them), so set package selector strings as translatable _( ... > ). You don't have to care about it at all. I will create the .pot-file today afternoon (as stated at yast-announce(a)opensuse.org) and it will be passed to the trandslators. After translated to individual lnaguages, it will be packaged into yast2-trans-XX. It doesn't require any work from your side, since yast2-gtk is already part of the Alpha snapshots. > * po/pt.po: created this translation; dunno how to make the thing > being used now... It can be removed, see above. However, I will grab this file to save the work of translatores since it is already done. Of course, volunteers for translations are always wellcome :-) Jiri 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

[yast-devel] Is this a bug of SUSE? Cannot load autoyast profile from harddisk,
by Da Shuang He 19 Jul '07

19 Jul '07

I make a bootable disk, and I can start to install the SUSE, but when it tries to find the autoyast file, it can't find it, and I write the kernel parameter like this : title SUSE 10 Installation root (hd0,0) kernel /boot/linux root=/dev/sda1 ramdisk_size=8192 install=hd://sda1/SUSE autoyast=device://sda1/autoinst.xml splash=silent showopts initrd /boot/initrd When I try autoyast=device://sda1/autoinst.xml, the error is , "An error occurred while fetching the profile: File /tmp/Yast2-02878-KeDBUh/tmp_mount/autoinst.xml cannot be found" And when I use file:///autoinst.xml and default, the error is, "An error occurred while fetching the profile: Reading file on /var/adm/mount//autoinst.xml failed. Reading file on /autoinst.xml failed. Reading file on CD failed. Path /tmp/Yast2-02878-KeDBUh/tmp_mount/autoinst.xml" And when I try to use hd://sda1/autoinst.xml It tells me hd is unknown protocol, Can someone tell how should I write the parameter for autoyast, or do you know somebody else can help me on this ? Or this is a bug of SUSE? -- 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] Next hackweek project done ... ycp-to-ruby-translator
by Klaus Kaempf 18 Jul '07

18 Jul '07

Hi, Cornelius hackweek proposal of a ycp-to-ruby-translator (see http://idea.opensuse.org/content/ideas/ycp-to-ruby-translator) was an itch I had to scratch sooner or later. So I spent some spare time and did a couple of late night hacks to make the translator real. It is based on an XML representation of the abstract syntax tree produces by the YCP scanner and parser within libycp. So its a pure syntax translator with only very, very limited knowledge of the semantics. The resulting Ruby code does pass the Ruby syntax checker, though. Combined with Duncans Ruby-YCP bindings, translating ycp to Ruby should be quite useful as we try to provide support for more widespread scripting languages. The translator is available at http://svn.opensuse.org/svn/yast/trunk/yxmlconv You need a recent version of yast2-core, which supports XML output and the '-x' parameter of ycpc. Then run ycpc -c -x file.ycp -o file.xml to convert YCP code to XML. Now use the xml-ruby translator as cd yxmlconv ruby src/converter.rb file.xml > file.rb Klaus P.S.: It's fairly straightforward to change the translator to output e.g. Python or Java or C# or ... --- 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

2 2

[yast-devel] YaST Icons
by Lukas Ocilka 18 Jul '07

18 Jul '07

Hi, I've found out that some YaST modules use icons that are not present in the "current" YaST theme. Because it's seemed to be impossible to find all manually (and it also didn't make any sense) I wrote a script that runs through all .ycp and .desktop files for "Icon". When the list of used icons is created, it searches for used icons in the current theme on the disk or in the directory provided as the first script parameter. The script doesn't work with Perl modules so it needn't check all icons used... Please, check your YaST modules for missing icons, thanks. See the attached script plus an example of script-output: /yast/test/iconcheck.sh /yast/CODE10/SL_10.3/source/theme/openSUSE/icons --- cut --- Icons will checked against /yast/CODE10/SL_10.3/source/theme/openSUSE/icons Checking files in directory: /yast/CODE10/SL_10.3/source/ca-management Processing file ./src/crl.ycp Processing file ./src/new_cert_items.ycp ... shortened ... Processing file ./src/wizards.ycp Processing file ./src/util.ycp All used icons (in YCP): ca-management No such file: /yast/CODE10/SL_10.3/source/theme/openSUSE/icons/22x22/apps/ca-management.png (yast-ca-management.png) No such file: /yast/CODE10/SL_10.3/source/theme/openSUSE/icons/32x32/apps/ca-management.png (yast-ca-management.png) No such file: /yast/CODE10/SL_10.3/source/theme/openSUSE/icons/48x48/apps/ca-management.png (yast-ca-management.png) Processing file ./src/ca_mgm.desktop Processing file ./src/common_cert.desktop All used icons (in desktop files): yast-ca_mgm yast-common_cert --- cut --- Bye Lukas -- Lukas Ocilka, YaST Developer (xn--luk-gla45d) ----------------------------------------------------------------- SUSE LINUX, s. r. o., Lihovarska 1060/12, Praha 9, Czech Republic

2 1

[yast-devel] test suite not run
by Martin Vidner 16 Jul '07

16 Jul '07

Hi hackers, thanks to a watchful user I noticed that one of my packages was not running the test suite while building. The problem is that if dejagnu is not installed, automake only prints this warning and goes on: WARNING: could not find `runtest' Simply add "BuildRequires: dejagnu" to *.spec.in (and then fix the test cases that broke in the meantime, bother...) These packages are affected*: libzypp-testsuite-tools yast2-ca-management yast2-ncurses yast2-online-update yast2-pkg-bindings yast2-slp *: cd /work/built/dists/all/i386/packs-i386; find . -maxdepth 3 -name Logfile.\* | LANG=C sort | xargs grep '^WARNING.*runtest' -- 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] Postponing metapackage/single click install to post 10.3
by Benji Weber 13 Jul '07

13 Jul '07

Greetings all, I unfortunately don't think it is going to be possible to get the metapackage handler / single click install feature ready for 10.3. The current situation is: - There is a version in factory with major bugs and incomplete functionality. - There is a version I'm working on using the new specification [http://en.opensuse.org/Standards/One_Click_Install] which I am unlikely to have time to complete within the next 2 weeks, as I am still working full time and moving house. As I understand it, alpha 6 (final alpha) freeze is this Friday. This is entirely my fault as I drastically underestimated the amount of time I would require to complete the implementation of the handler for the finalised specification of the metapackages, and consequently wasted too much time working on a ycp -> codedom project. I have hit a number of problems that have delayed me considerably, particularly as with mvidner away there is no YCP guru on IRC. Causing me particular delays at present are: - Buggy/undefined behaviour of yast2-pkg-bindings, particularly deleting packages and some of the resolvable functions seem to not be working properly at all, but debugging these is slow. I will post testcases when I have them. - YCP's lack of object orientation means even the simplest additional feature in the XML tends to lead to a ballooning of fragile logic within the handling code. Even with the YCPXML helper to hide the lists of maps of lists mess it is taking me far too long just to write code that works at all, let alone robust or testable. There is also a considerable amount of work to do even if development were complete, for example chasing getting mimetype associations into each browser package. Given the problems I am encountering and given our timescales I think the only option now may be to delay inclusion of this to post-10.3 and re-think the design. Probably implement the XML handling and communication with package manager in some other language/platform and possibly use YCP/YaST just for the GUI. We can also watch what ubuntu are doing with their similar project [http://www.cypherbios.org/blog/?p=41&language=en] and see if we can learn any lessons. Any advice is appreciated. _ Benjamin Weber -- 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] 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