YaST Development January 2011

yast-devel@lists.opensuse.org

17 participants
6 discussions

[yast-devel] Direction of YaST Architecture?

by Arvin Schnell

Hi, in a recent telco the question about the direction of the YaST architecture was raised. In the pase a lot of things have been tried. E.g. integrate different languages (Perl, Python, Ruby), try different build systems (cmake), automatic generation of bindings for C/C++ libraries (libstorage) or simply use common technologies (e.g. CIM). This is not necessarily bad but from my point of view quite a few ideas are stuck halfway (Python integration) or are simply of bad quality (generation of bindings). Even usage of Perl seems to be considered to be no improvement. But instead of removing failed approches we keep them and often do not even look at better ways. As a result the YaST architecture is on one hand more complex and confusing then required and on the other hand lacks quality and features. So now that we have minimal recourses to improve the YaST Architecture we should concentrate on a few improvements instead of dissipate our energies again. So what seems desirable and feasible? Some ideas: 1) Replace YCP with some common language? With more that 100 modules this looks impossible. 2) Allow a common language next to YCP? A good integration seems difficult. 3) Improve YCP (at least fix bugs)? Do we want that? 4) Better bindings of C/C++ libraries for YCP? Other suggestion? Of course we already have a list of ideas (only few about the architecture), see: http://old-en.opensuse.org/YaST/Development/Research Discussion is opened. ciao Arvin -- Arvin Schnell, <aschnell(a)suse.de> Senior Software Engineer, Research & Development 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

10 years, 5 months

[yast-devel] Top 10 Web-Security Vulnerabilities and Remediation

by Thomas Biege

Hello, the following link summarize the top 10 web-security vulnerabilities, gives examples and hints about avoiding them. Enjoy reading! http://www.owasp.org/index.php/Top_10_2010-Main Bye Thomas -- Thomas Biege <thomas(a)suse.de>, SUSE LINUX, Security Support & Auditing SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nuernberg) -- Wer aufhoert besser werden zu wollen, hoert auf gut zu sein. -- Marie von Ebner-Eschenbach -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

10 years, 5 months

[yast-devel] [PATCH] Edit complete URL by default

by Michal Marek

Separate input boxes for the protocol, host name and directory path might have been intuitive in the 90's, when typing commands into the 'ftp' program was a common way of retrieving files from the internet, but it is definitely not intuitive for most of today's users. Signed-off-by: Michal Marek <mmarek(a)suse.cz> --- /usr/share/YaST2/modules/SourceDialogs.ycp.orig 2011-01-19 17:54:03.000000000 +0100 +++ /usr/share/YaST2/modules/SourceDialogs.ycp 2011-01-19 17:54:14.000000000 +0100 @@ -1374,7 +1374,7 @@ // use selected editing URL part, remember the value in case the URL is wrong // and the dialog needs to displayed again -boolean editing_parts = true; +boolean editing_parts = false; /** * Handle function of a widget -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

10 years, 6 months

[yast-devel] Update WebYaST docu in Wiki

by Stefan Schubert

Hi, in the last view days I have moved the *complete* WebYaST docu from http://old-en.opensuse.org to http://en.opensuse.org/WebYaST At the same time I have cleaned up the docu. If anything is still missed please add it. So I would like to declare the old-wiki WebYaST pages to "frozen" and not needed anymore. Greetings Stefan -- ******************************************************************************* Stefan Schubert SUSE LINUX GmbH - Maxfeldstrasse 5 - D-90409 Nuernberg, Germany e-mail: schubi(a)suse.de ------------------------------------------------------------------------------- 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

10 years, 6 months

[yast-devel] YaST and Accessibility Discussion

by Bryen M. Yunashko

Hi folks, There was a gentleman I met at the openSUSE Conference who said he worked on the YAST team and dealt with some a11y issues a while back. Tragically, I cannot remember the name of this gentleman. (Are you here??) I wanted to reach out to him, or to any of you who might be interested, to invite you to join in a meeting with various folks who are interested in improving accessibility on openSUSE. it isn't going to be a formal meeting, just a gathering of people to assess what our current issues are. Out in the wild, we have some interesting opportunities, and part of the blockers is that people with special needs are currently unable to install openSUSE. In fact, openSUSE has a very bad reputation in the accessibility community and I'd like to see that perception reversed. You can see my article talking about this meeting on Thursday on IRC here http://news.opensuse.org/2011/01/06/putting-our-accessibility-heads-togethe… . The meeting will be in the #opensuse-a11y IRC channel at 17:00 UTC. I hope to see at least one of you from the YAST team representing at the meeting. Thanks! Bryen M Yunashko -- To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org For additional commands, e-mail: yast-devel+help(a)opensuse.org

10 years, 6 months

[yast-devel] Building packages in OBS YaST:Head in openSUSE_Factory_zypp_Head repo

by Ladislav Slezak

Hi all, I'm thinking about openSUSE_Factory_zypp_Head repo in YaST:Head OBS project. Do we really need to rebuild all yast packages once more for the latest libzypp? I mean, currently there are 124 packages in total, but only few of them actually depend on libzypp (pkg-bindings, *-pkg, kupdateapplet), if we disabled the remaining packages the build server would save quite a lot of build power. Rebuilding complete YaST on 2 archs (i386 + x86_64) needs to rebuild ~250 packages. Users who use the latest libzypp (from libzypp Head) would need to add both YaST repos (openSUSE_Factory and openSUSE_Factory_zypp_Head), but I guess there are just few of them (if any). So my proposal is to build only the minimal amount instead of all packages in openSUSE_Factory_zypp_Head repo. Your opinions? -- 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

10 years, 6 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

YaST Development January 2011