Hello Lukas, On 2020-08-10 16:40, Lukas Ocilka wrote:
On 8/10/20 4:07 PM, Stefan Hundhammer wrote:
On 2020-08-10 15:51, Lukas Ocilka wrote:
Hopefully (anything we'll do) we'll use as much upstream as possible. NIH syndrome should not apply here.
When I look at our current YaST modules, I see an awful lot of NIH: So many of them are just a thin wrapper around existing tools. So if we are taking this seriously, we should get rid of YaST modules that are really just duplicating functionality that is already available in some other form.
This is quite off-topic, please start another thread if necessary.
you started talking about "NIH" and Stefan replied to that so in the end you started getting "quite off-topic" ;-)
yast-printer, anyone? Or yast-apparmor? To name just a few.
Side note 1: Both actually have valid use-case: AutoInstallation. Side note 2: Neither of them were written by YaST developers.
Your side note 2 is plain wrong, not helpful, and "very off-topic". The YaST printer module was written and maintained all the time by YaST developers until its last YaST developer left SUSE (I think I remember he even was laid off) and no other YaST developer took over maintainership so in the end I had to take it because at that time its YCP code was my experimental printer module code that replaced the official YaST printer module by its last YaST developer (because my experimental code was already better than the official pile of old grown code cf. https://en.opensuse.org/Archive:YaST_Printer_redesign) and because I was the one who got basically each and every printing related bug assigned I needed to further enhance my experimental code into something that doesn't cause too many new bugs. Then some YaST developers converted my YCP code into some generated "Ruby kind of code" that I neither speak nor understand. I even wasted one of my SUSE HackWeeks to learn Ruby but I don't like Ruby and some basic Ruby knowledge does not really help to actually maintain that generated Ruby kind of code. In practice the YaST printer module is no longer acually further developed since it was "converted from YCP to Ruby by YCP Killer" that happened in July 2013, see the yast2-printer.changes entry ---------------------------------------------------------- Wed Jul 31 08:37:43 UTC 2013 - yast-devel@opensuse.org - converted from YCP to Ruby by YCP Killer (https://github.com/yast/ycp-killer) - version 3.0.0 ---------------------------------------------------------- at https://build.opensuse.org/package/view_file/YaST:Head/yast2-printer/yast2-p... My last change is dated Mon Jan 19 14:51:39 UTC 2015 and my last actual further development enhancement are dated before it was "converted from YCP to Ruby by YCP Killer". Since that time the YaST printer module is kept working as is as far as possible with reasonable effort by YaST team members who know about how to deal with their generated Ruby code. Since my YCP code was converted into generated Ruby code it is no longer my code and it is no longer code that I could further develop with reasonable effort. Because the YaST printer module is based on the traditional way how printing works with CUPS <= 1.5.4 in particular for printing in the network, the YaST printer module intentionally fails with error messages when things won't work with nowadays way how printing in the network works with CUPS >= 1.6 cf. "CUPS >= 1.6 has major incompatible changes" in https://en.opensuse.org/SDB:CUPS_in_a_Nutshell So the YaST printer module is outdated for printing in the network. See also https://lists.opensuse.org/yast-devel/2015-03/msg00044.html and https://features.opensuse.org/308045 https://features.opensuse.org/316789 The links to features.opensuse.org fail with "openSUSE deprecated service" - nomen est omen.
--
Lukas Ocilka, Systems Management Team Leader & YaST Product Owner SLE Department, SUSE Linux
🌲 Please consider the environment before printing this e-mail ☂ Handle with care - Your reply can be stored in the cloud 😱 Pie-chart is just a representation of randomly chosen data
⚠ IMPORTANT: The contents of this email and any attachments are confidential. They are intended for the named recipient(s) only. If you have received this email by mistake, please, notify the sender immediately and do not disclose the contents to anyone or make copies of thereof.
Wow - I am impressed by so much IMPORTANT information - yeah! Kind Regards Johannes Meixner -- SUSE Software Solutions Germany GmbH Maxfeldstr. 5 - 90409 Nuernberg - Germany (HRB 36809, AG Nuernberg) GF: Felix Imendoerffer -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org