http://bugzilla.novell.com/show_bug.cgi?id=561324
http://bugzilla.novell.com/show_bug.cgi?id=561324#c0
Summary: YaST Coding style not followed by yast2-devtools nor tutorials Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: All OS/Version: All Status: NEW Severity: Minor Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: felix.wolfsteller@intevation.de QAContact: jsrain@novell.com Found By: --- Blocker: ---
User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.0.15) Gecko/2009102815 Iceweasel/3.0.6 (Debian-3.0.6-3)
New to YaST (module) development, my natural starting point was one of the "official" tutorials (e.g. http://en.opensuse.org/YaST/Tutorials, but actually the comprehensive http://forgeftp.novell.com/yast/doc/SL11.1/tutorials/).
Wanting to confirm to (imho important) style and coding guides, I looked at the well done http://forgeftp.novell.com/yast/doc/SL10.1/codingrules/index.html and was surprised that the tutorial and the yast2-devtool pointed me a "wrong" (regarding coding style) direction.
I found the main problem with the devtools to be the skeletons (e.g. http://svn.opensuse.org/svn/yast/trunk/devtools/devtools/skeletons/config/sr... ). A quick improvement of the Tutorials would be to mention that there is a style guide that should be read and applied, while apologizing that the tutorial in current state does not reflect that in every case.
In an discussion in irc it was mentioned that reworking the tutorial (and i guess the config skeleton) might be a great Junior Job (JJ), as it automatically brings you closer to YCP.
Thanks to jreidinger, kobliha and jsuchome from the #yast irc channel.
Reproducible: Always
Although the links in my post point to specific versions (e.g. openSUSE 11.2, SLE10.x) i found the tutorials of all versions to be affected.
I am sorry to be picky.
http://bugzilla.novell.com/show_bug.cgi?id=561324
http://bugzilla.novell.com/show_bug.cgi?id=561324#c1
--- Comment #1 from Felix Wolfsteller felix.wolfsteller@intevation.de 2009-12-07 15:47:32 UTC --- Automatic code formatting might be possible (e.g. with indent, astyle or the like). If so, fixing the code in the tutorials and the devtool-skeletons would be pretty easy. If it proves to be of value, the correct syntax to call one of these tools might be added to the style-guide (and the tutorial).
http://bugzilla.novell.com/show_bug.cgi?id=561324
http://bugzilla.novell.com/show_bug.cgi?id=561324#c
shuang qiu sqiu@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |sqiu@novell.com AssignedTo|bnc-team-screening@forge.pr |yast2-maintainers@suse.de |ovo.novell.com |
http://bugzilla.novell.com/show_bug.cgi?id=561324
http://bugzilla.novell.com/show_bug.cgi?id=561324#c2
Thomas Göttlicher tgoettlicher@novell.com changed:
What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|yast2-maintainers@suse.de |mvidner@novell.com
--- Comment #2 from Thomas Göttlicher tgoettlicher@novell.com 2009-12-09 14:37:06 UTC --- Reassigning to yast2-devtools maintainer.
https://bugzilla.novell.com/show_bug.cgi?id=561324
https://bugzilla.novell.com/show_bug.cgi?id=561324#c3
Lukas Ocilka locilka@suse.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |CLOSED CC| |locilka@suse.com Resolution| |WONTFIX
--- Comment #3 from Lukas Ocilka locilka@suse.com 2012-01-04 09:09:18 UTC --- I'm afraid that Martin will not have time to fix this in a near future.
If you are still interested in this topic, please, write to yast-devel@opensuse.org and identify the places where tutorials (etc.) do not follow the coding style and/or send a patch if possible.
Thanks Lukas