On Wed, 25 Sep 2013 15:20:46 +0200 Arvin Schnell wrote:

On Wed, Sep 25, 2013 at 03:09:01PM +0200, Josef Reidinger wrote:

...

Hi, I plan to clean a bit ... ergh, clean almost whole yast2-devtools. At first I would like to mention why I think it is important and what is benefits and then how I would like to do it.

...

So please write which tools from yast2-devtools you use for current master development and how you use it. If you don't write it, there is quite big chance that such tool will be removed.

ycp_puttext is needed once in a while. Should of course be updated to work with Ruby.

Regards, Arvin

Thanks Arvin, interesting tool, I don't know about its presence. Porting to ruby sounds reasonable. Maybe rename it to better name like patch_proofread? Josef -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org

On Wed, 25 Sep 2013 16:05:05 +0200 Ladislav Slezak wrote:

Dne 25.9.2013 15:09, Josef Reidinger napsal(a): [...]

...

So please write which tools from yast2-devtools you use for current master development and how you use it. If you don't write it, there is quite big chance that such tool will be removed.

What I use regularly:

- showy2log tool for displaying colorized y2log, I always have an open terminal window on my desktop running "y2tool showy2log -- tail -f" command.

OK, makes sense.

- ycp.vim - YCP syntax highlighting for vim (although we switched to Ruby it should be kept for SLE11 maintenance)

This is tricky as you cannot use current devtools for SLE11 maintenance because we change tools for generating configure as we don't want here stuff for ycp, but in SLE11 we want it. I think we should do maintenance in container, VM or at least in chroot.

What I have not used for long time (but still could be useful):

- oscsubmit - for submitting a package to OBS, but with CI integration it probably become obsolete and with new rake tasks it won't make sense anymore

yes, agreed

- pot-spellcheck - checks spelling, it can find typos in user visible texts (button labels, help texts...), it has a custom dictionary so it does not report false positives for Yast specific terms ("AutoYaST", "linuxrc", "hwinfo"...)

I have implemented something similar using Rake in Webyast and SLMS, so maybe it could be moved to the yast rake tasks instead of maintaining this script...

yes, I think it should be part of checks in rake.

- for-proofread - creates a diff POT file, so if you add some new strings you can easily send only the new ones to translators (instead of sending complete POT file) (But I do not know whether it is currently needed, maybe it's obsolete, we should ask Karl...)

Can you ask please? Thanks Josef

--

Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE

-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org

On Wed, 25 Sep 2013 16:53:21 +0200 Ladislav Slezak wrote:

Dne 25.9.2013 16:25, Josef Reidinger napsal(a):

...

On Wed, 25 Sep 2013 16:05:05 +0200 Ladislav Slezak wrote: [...]

...

- ycp.vim - YCP syntax highlighting for vim (although we switched to Ruby it should be kept for SLE11 maintenance)

This is tricky as you cannot use current devtools for SLE11 maintenance

Yes, I know, but I can still use vim, git and other tools directly from my workstation which is very convenient. And I also do not need to copy my config files (like ~/.vimrc) to the VM.

Of course, for creating the final tarball I need a VM, but it can contain just a minimal system plus some yast devel packages needed for running "make -f Makefile.cvs && make package-local" and nothing else.

OK, that leads me to another nice idea, that we should split devtools and buildtools. Reason is quite simple. Buildtools is dependency of all yast modules ( so include stuff like rpmmacros or y2automake or rspec ) and need to contain almost none dependencies. On otherside devtools should take advance of various tools available from ruby world ( so nice CLI framework, metric fu for metrics of ruby code and various other stuff like syntax highliting you mention). Another nice sideeffect is that it is more logic for newcommers, that buildtools can be ignored as it is used only in build service and devtools is set of nice tools to help with yast development. Josef

--

Ladislav Slezák Appliance department / YaST Developer Lihovarská 1060/12 190 00 Prague 9 / Czech Republic tel: +420 284 028 960 lslezak@suse.com SUSE

-- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org

On Thu, 26 Sep 2013 17:23:14 +0200 Martin Vidner wrote:

On Wed, Sep 25, 2013 at 03:09:01PM +0200, Josef Reidinger wrote:

...

So please write which tools from yast2-devtools you use for current master development and how you use it. If you don't write it, there is quite big chance that such tool will be removed.

doxygen/ydoxygen factors out the common parts of doxygen configuration yast2/*ycp-mode.el Emacs!

There are other pieces like y2automake and y2autoconf, but you will know pretty quick if you break those :)

Yeah, I want to know tools that you use directly, not tools that is run underneat. So e.g. y2automake can die only if we kill all our autotools based building. Josef