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
Hi,
in short, I add in ruby bindings automatic inclusion of "dir"
repositories in Y2 paths to ruby load path. Reason is to have common
place to have pure ruby private ( in sense of not share it with rest of
ruby world ) files. Its intended usage is for various modules, classes
and other stuff that makes your plugins nicer. Include directory is not
good as it contain now translated code and contain some special magic
to make it work in ycp-way.
Namespace is shared between plugins so it make sense to use own
namespace there same way as in "include" directory.
Thanks locilka for initial idea.
Long story:
For code now there is modules, clients and includes. Modules is
intended for modules that share its functionality over component
system. You can import it. Clients is scripts, that can be executed by
Yast2 environment. Include is tricky as it is code snippets that is
internally shared, but it has few limitations - It must be included in
code, it must be ensured that it is included only once, so it is very
limited compared to ruby ( or perl, python ) ability to share code
parts.
That leads to idea, that we need directory where you can have
proprietary parts of code that is intended only for given module and
its usage depends on language.
Current status is that it is supported only in ruby-bindings, but plan
is also to add it to perl and python bindings, if there is someone who
is interested in it (e.g. now in perl it must be all in one file or
use some tricky loading or write upstream perl library, that can be
called).
Example demonstration ( not working, just to demonstrate, real example
comes after Milestone 4 ):
client C:
require "services/main_dialog"
data = Services.load
dialog = MainDialog.new data
result = dialog.run
if result == :ok
Services.save dialog.data
end
return result
dir/services/main_dialog.rb:
require "yast"
class Services
attr_reader :data
def initialize
...
end
def run
...
end
end
Josef
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi,
we are pleased to announce that the final Ruby conversion of YaST YCP
code to Ruby is over. The converted source was committed to Git [1],
passed through Jenkins and builds successfully in YaST:Head [2]. YaST
version was increased to 3.0.0. We also sent submit requests to Factory
(not accepted yet).
** YaST Git repositories are open for development again. **
Thanks everybody for patience and welcome to the new Ruby era :-)
Technical Details
-----------------
In all affected Git repositories, we used the following Git tags to mark
the conversion:
* good-bye-ycp -- last commit before the conversion
* hello-ruby -- last commit of the conversion
You can use them to see the changes the conversion did, e.g.:
https://github.com/yast/yast-yast2/compare/good-bye-ycp...hello-ruby
The amount of converted code is quite impressive:
* 4204 files
* 594680 lines of YCP deleted
* 724687 lines of Ruby added
Issues
------
There are few small issues that remain to be solved:
* There were problems running tests on Jenkins for several packages.
We solved them temporarily by fiddling with the test scripts, but
we need to fix them more properly. Josef & Martin will look into
that.
Note the tests still pass correctly in when building in the OBS.
* Module "iplb" is currently broken -- it wasn't converted, but its
tests don't work after converting "testsuite" into Ruby. We need to
clarify status of this module and fix it or drop it.
Next Steps
----------
In the coming days and weeks, we would like to do the following:
1. Publish a document describing what the conversion changed (and
how) and what remained the same. This will make starting with Ruby
YaST easier for everybody who was not involved in the conversion.
2. Publish a document describing how to best handle YaST maintenance
fixes in the old YCP code base which will need to be applied back
to Ruby.
3. Decide on how exactly to do documentation and testing.
4. Update the skeleton that shows how to create a new YaST module to
Ruby and describe the best practices.
5. Initiate a discussion about further changes and improvements in
YaST architecture, which would allow us simplify it even more and
make YaST even more attractive to contributors.
[1] https://github.com/yast/
[2] https://build.opensuse.org/project/show/YaST:Head
--
David Majda
SUSE Studio developer
http://susestudio.com/
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org