Hi all,
Yesterday I published a short blog post about recording a screencast
(a desktop session) to create a video or an animated image.
So if you want to have nice animated images in READMES [1] or in pull requests [2]
then check this post [3].
Enjoy!
[1] https://github.com/lslezak/build-rake/blob/master/README.md
[2] https://github.com/yast/yast-registration/pull/240
[3] http://lslezak.blogspot.cz/2016/01/recording-screencast-in-linux.html
--
Ladislav Slezák
Appliance department / YaST Developer
Lihovarská 1060/12
190 00 Prague 9 / Czech Republic
tel: +420 284 028 960
lslezak(a)suse.com
SUSE
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi,
I have noticed a quite interesting GitHub feature which allows to protect
the specified branches. A short summary from [1]:
A protected branch:
- Can't be force pushed
- Can't be deleted
- Can't have changes merged into it until required status checks pass
- Can't have changes merged into it until required reviews are approved
- Can't be edited or have files uploaded to it from the web
See [1] and [2] for more details.
AFAIK some developers use forks mainly because they are afraid of messing
the original repositories. With protected branches that should not happen.
Additionally it would strictly enforce PR reviews (we do that already
so I see no problem with that).
IMHO a nice feature, I'm just not sure which branches we could protect.
Obviously the old maintenance branches, I'm not sure about the "master"
branch, maybe it would be too strict.
What do you think about it? Should we use this GitHub feature?
We could use the agile approach, try it in a few selected repos and see
how it works...
Comments?
[1] https://help.github.com/articles/about-protected-branches/
[2] https://help.github.com/articles/configuring-protected-branches/
--
Ladislav Slezák
YaST Developer
SUSE LINUX, s.r.o.
Corso IIa
Křižíkova 148/34
18600 Praha 8
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hey guys,
I started to work on libyui-ncurses and I'm facing a dependency problem.
I build the rpm package with rake, as described on
https://github.com/libyui/libyui-ncurses, but when I try to install it
with zypper, I receive the following message:
Problem: nothing provides
libncursesw.so.6(NCURSESTW6_5.7.20081102)(64bit) needed by
libyui-ncurses7-2.48.0-1.x86_64
I'm using OpenSuse Leap 42.2
Do you know how can I overcome this dependency? :-)
BRs,
Gilson
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hello there,
I initially asked the question in opensuse-factory ML (1) but may be
somebody here could help me on this investigation.
(1) https://lists.opensuse.org/opensuse-factory/2016-11/msg00497.html
--
Michel Normand
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
Hi all,
I have improved the Ruby debugger integration in YaST, if you install
the latest yast2-ruby-bindings package (version 3.2.2+) then
you can use a keyboard shortcut to start the Ruby debugger anytime.
Simply press Shift+Ctrl+Alt+D and the Ruby debugger will pop up
in a new window.
Limitations:
- Works in Qt UI only (ncurses is not supported)
- It's hooked to the UI.UserInput call (and similar), so if the
code is stuck the debugger cannot be started
This is the debugging feature which I always wanted to have, so enjoy it!
More details:
https://github.com/yast/yast-ruby-bindings/pull/179http://yastgithubio.readthedocs.io/en/latest/debugging/#using-a-keyboard-sh…
--
Ladislav Slezák
YaST Developer
SUSE LINUX, s.r.o.
Corso IIa
Křižíkova 148/34
18600 Praha 8
--
To unsubscribe, e-mail: yast-devel+unsubscribe(a)opensuse.org
To contact the owner, e-mail: yast-devel+owner(a)opensuse.org
