I want to fix yast2-slide-show for SLE11 SP3. Which git commands do I
have to use, please?
Thus far, I have checked out trunk only.
--
Karl Eichwalder SUSE LINUX Products GmbH
R&D / Documentation Maxfeldstraße 5
90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hello,
Can any tell me please, witch packet i have to install for the "graphic" in
console Mode
There is a missing dependency for the correct drawing the frame ?.
This is a minimal Install and running in init 3 mode.
Thanks :)
--
mit freundlichen Grüßen / best Regards,
Günther J. Niederwimmer
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi,
I'm looking for documentation or a guide on how to write a yast module. Is
there anything available? Or is there a module you'd recommend to look at first?
Regards,
Nanuk
--
Nanuk Krinner - Systems Management Engineer
SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuernberg
Tel: +49-911-74053-577 - nkrinner(a)suse.de
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi,
I would like to announce, that new version of ruby bindings (3.1.2) is
released. There is two changes:
1. Detect if there is invalid response type from client ( client call
using component system, so only simple types are allowed ) -
https://github.com/yast/yast-ruby-bindings/issues/81
2. Improved exception handling. Now if exception appear in client, then
error message about internal error is shown to user. It using
Report.Error so it works good in various cases ( TUI, autoyast, CLI ).
After report it works as before, so client return nil and continue.
Reason for this change is to reduce number of silent failures and
encourage everyone to use exceptions in yast code.
I think we need some rules for exceptions. My proposel is to use
exceptions everywhere and every uncaught exception is bug. This
behavior allows us to quickly see problem and do not have current
silent failures.
Josef
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi,
today I plan to modify jenkins to do this stuff. It was done only
partial, because when my script run, maintenance update of jenkins
start ( I get no info that it is planned, Daniel and Bernhard added to
CC ). So some job have it and few doesn't.
I plan to run script again on Monday, so all jobs will have it. To not
loose the script add it to devtools[1], so next time it will be faster
( now it took me with writting script and reading API documentation
around half of hour ) and everyone can reuse it.
Josef
[1] https://github.com/yast/yast-devtools/pull/39
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi,
I attend to Prague openSUSE release party where I also have
presentation about yast in ruby, new installer and future plans. Party
was good and I enjoy it. I heard there some feedback about Yast so I
would like to share it with you.
In general community are show some interest in restarted
documentation, new test suite and separated libyui. There was question
in what state is documentation ( response is that it is work in
progress and we will update it on demand or in free time ). There is
also shown some interest in new installer.
My feeling is that around four people shown some interest about yast
developement and will look at it ( I provide some links and contact
how to reach us). I was also stopped by one student who show some
interest to make a magister diploma thesis with something related to
Yast. I only have idea about libyui ui generator and separate ui
definition, but if anyone else have idea lets share it. I think we can
reuse it for GSOC where we can attract additional community developers.
Josef
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi,
after my latest debugging of installer failure I found one important
thing how clients works in Yast. It behaves like scripts, but with one
big difference -> if invoked via WFM.Call then it is not completelly
thrown away.
It have benefits like storing some data, but one big drawback. You can
mess global namespace during run of script. And exactly this happen in
the latest issue. I use `include Yast` on top level and it includes all
modules to global namespace. Result is collision between
Yast::FileUtils and ::FileUtils in ruby, which is used for file
manipulation.
So my general recommendation is to not use global namespace in scripts
and also in other places, otherwise you risk collission with ruby
own libraries.
Example of my fix can be seen in [1]
Josef
[1] https://github.com/yast/yast-network/pull/135
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi,
I choose from ruby weekly news these two articles that can be
interesting for yast development.
The first one is about iterative building of collection like create
array from another array. I still see it often in code, so it is nice
introduction how you can do it.
http://robots.thoughtbot.com/iteration-as-an-anti-pattern/
Ideally you should stop yourself before each `each` statement you write
what you want achive and use it only if you want tell object to do
something.
The second one is advanced tips for rspec. Especially I recommend to
read rspec style guide -
https://github.com/howaboutwe/rspec-style-guide but there is also other
interesting tips ( like profilling how long your test took ).
http://blog.joshsoftware.com/2013/11/23/pro-tips-for-writing-better-rspec-t…
I hope you enyou articles.
Josef
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi,
after series of dropping module I decide that maybe it is now good time
to check how much code we have in Yast.
short summary:
total 921k
ruby 674k
perl 87k
C/C++ 160k
total cound (together with command to verify it on git checkout via
yast-mass )
`find . | grep -e "\.rb$" -e "\.pl$" -e "\.pm$" -e "\.h$" -e "\.c$"
-e "\.cpp$" -e "\.hpp$" -e "\.cxx$" -e "\.cc$" | xargs wc -l`
=> 921137 lines
ruby files
`find . | grep -e "\.rb$" | xargs wc -l`
=> 674068
perl files
`find . | grep -e "\.pl$" -e "\.pm$" | xargs wc -l`
=> 86843
C/C++ ( can contain some generated code by swig, flex, bison, etc. )
`find . | grep -e "\.h$" -e "\.c$" -e "\.cpp$" -e "\.hpp$" -e "\.cxx$" -e "\.cc$" | xargs wc -l`
=> 160226
So as you can see yast is really non-trivial project and any help to
yast team is welcome :)
Josef
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi Yast hackers,
please ignore email about failures in jenkins until yast2-pkg-bindings
will be rebuild. In our OBS against which we do test build is currently
in inconsistent state causing failure of any build. I will manually
trigger rebuild of all failed packages when OBS will get back to
working state.
Josef
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org