January 2023 - YaST Development - openSUSE Mailing Lists

yupdate now also supports live medium (D-Installer) and containers (ALP)
by Ladislav Slezák 12 Jan '23

12 Jan '23

Hi all, I have enhanced the yupdate [1] script to work also in live medium or in containers [2]. That means you can use it for patching the D-Installer or the YaST modules included in the ALP container directly from GitHub or your local Git checkout. For using it in the D-Installer connect to the running instance via SSH or switch to the first console. (Use root/linux credentials.) Using in a container is a bit more complicated as podman does not allow to pass additional options to the "runlabel" command. Use podman container runlabel --display run <image> to display the start command. Then copy & paste that command to terminal and add the "--entrypoint=bash" option to start a shell instead of the YaST Control Center. Then patch the system using yupdate and start YaST manually ("yast" or "yast <module>"). If you use docker then run this command to print the start command: docker inspect --format '{{index .Config.Labels "RUN"}}' <image> (Do not forget to replace the "/usr/bin/podman" at the beginning and the "IMAGE" placeholder at the end. :-)) See more details in the yupdate documentation [3]. [1] https://github.com/yast/yast-installation/blob/master/bin/yupdate [2] https://github.com/yast/yast-installation/pull/1073 [3] https://github.com/yast/yast-installation/blob/master/doc/yupdate.md -- Ladislav Slezák YaST Developer SUSE LINUX, s.r.o. Corso IIa Křižíkova 148/34 18600 Praha 8

1 0

CUBE for organizing D-Installer's CSS
by David Díaz 11 Jan '23

11 Jan '23

Hi there! During Christmas, I came across the CUBE CSS[1] methodology and found it simple and straightforward. I also watched the interesting "Be the browser’s mentor, not its micromanager"[2] talk from its author. I suggested applying it in the D-Installer web UI[3]. We have barely introduced the term and gotten rid of a few things to start accommodating the CSS in those layers: Composition, Utilities, Blocks, and Exceptions. For sure, we have to choose better names for CSS classes too. Oh! Naming things... always the hardest part![4] BTW, talking about layers, Did you know about CSS @layers[5][6][7]? I did not. Among other impressive CSS features[8], it looks promising. I can foresee D-Installer itself making use of them for helping with frameworks overrides and theming :) Cheers! [1] https://cube.fyi/ [2] https://www.youtube.com/watch?v=5uhIiI9Ld5M [3] https://github.com/yast/d-installer/pull/391 [4] https://xkcd.com/910/ [5] https://drafts.csswg.org/css-cascade-5/#layering [6] https://www.smashingmagazine.com/2022/01/introduction-css-cascade-layers/ [7] https://ishadeed.com/article/cascade-layers/ [8] I know, I have been disconnected from the web evolution for a long time already. The good part is that now I'm so excited about almost every article I read. Let's see how much I'm able to keep surfing the wave :P -- David Díaz YaST Team at SUSE LINUX GmbH IRC: dgdavid

1 0

YaST API to resolve short hostname to resolvable FQDN
by Gaurav Kumar 11 Jan '23

11 Jan '23

Hello Team, Is there any API in YaST to resolve the short hostname to get resolvable fully qualified domain name (FQDN) ? For example, if the short hostname is set to server1, then how do we get the resolvable name of server1.example.com I have gone through the yast2-network module and was not able to find any suitable API specific for the above task. Is there any YaST call present which I can utilize. Regards, Gaurav

2 1

Codebase(s) and Branch(es)
by Lukas Ocilka 02 Jan '23

02 Jan '23

Hi there, Our current approach so far was to keep all the development in a single branch. This also conforms to the Factory First Policy. This meant Tumbleweed, Leap 15.5, SLE 15 SP5, and also ALP I've learned, that we need to make incompatible changes because of, e.g., dropping Wicked from ALP and Tumbleweed and replacing all with NetworkManager. This would mean splitting into two codestreams and two branches: Edge: Tumbleweed, ALP (Factory First) Stable: Leap 15.5, SLE 15 SP5 (No Factory) We still expect that there will be quite some development in the Stable branch for some time. Of course, bugfixes go to all "applicable" branches where it makes sense anyway. So, is this doable? Do we have resources to keep them in "sync" - but already different? Can we keep both installers at the same time in Edge till D-Installer is mature enough? Thx Lukas -- Lukas Ocilka, Systems Mgmt & Consulting Team Leader & YaST Product Owner SLE Department, SUSE Linux

2 4