Any thoughts or experience on adding Yast back into Leap 16, as a user or ???
Did SUSE remove Yast to intentionally push non-paying desktop users towards OpenSUSE’s other options—like Slowroll or Tumbleweed?
See Re: Will YaST be deprecated in Tumbleweed? - openSUSE Factory - openSUSE Mailing Lists
Short version: Those who want YaST to continue need to step up and contribute code, because a lot of the codebase is unmaintained.
5 Likes
With OpenSUSE on its biggest user upswing in a long-long time, this is the wrong time to be abandoning those things that make it easy to adopt. I was working on a script for a video on OpenSUSE being the best beginner distro–regardless of your use case, but that project is shelved pending a GUI tool resolution.
3 Likes
Which YaST modules most added value for you?
You might review the thread and this discussion:
There are some pretty significant reasons behind the decision (as it stands now) outlined in the mailing list discussion. There are over a hundred modules that need to be maintained - if there aren’t enough people willing to maintain it, then it’s not going to survive.
Support doesn’t just magically happen. People need to step up and offer to help.
1 Like
C’mon, really. Do not overestimate your importance.
The reason is likely simpler. SUSE decided that (some/most of) YaST modules are not important for the paying customers and so is not allocating resources to maintain them. As long as Leap is just a byproduct of SLE (or whatever it is/will be called now) non-paying desktop users are affected too without SUSE even being aware of it.
What makes you think YaST is maintained in Tumbleweed? The only difference is - Leap 16 is based on SUSE commercial offering, SUSE is not willing to accept responsibility to maintain obsolete software for another decade and so does not include it. Tumbleweed does not care as long as this software still builds - but then, it also does not really guarantee that it works.
1 Like
@LanceHaverkamp Use Cockpit…
This is a very interesting discussion …
I am a simply user and one of the important reasons for choosing openSUSE about 20 years ago, was YAST (particularly YAST2). If it is now and will be no more maintained, it is not good in my opinion.
Altogether I understand the reasons of SUSE, not to maintain YAST even if I cannot understand, why the paying customers do not find it important. Maybe they have are bis company, which can pay a staff of OS maintainers, while a lot of simply users need graphical tools like YAST.
Therefore software developer and maintainer are becoming less end expensive. The best ones are being caught by the Silicon Valley’s oligarchs…
Anyway, I think, it could be a solution letting pay the “simply users” a little (?) contribute for some tools or for the whole openSUSE Leap. But there are some contras to this possibility:
a) It has been tried about 15 years ago (based on Mandrake?), but it failed due to lack of interested.
b) OpenSUSE Leap will be replaced with KALPA (or similar)
What are the most important YAST modules for me?
- Install / Deinstall / Configure software (sw_single_wrapper)
- OneClickInstallUI
- Repositories Management
- Install / Deinstall / Configure Printers and Scanners
- Configure Bootloader
- Firewall management
- Management of Users and Groups
- Computer (Re-)name
NOT YET BUT MAYBE IN THE FUTURE
Samba server
NTP configuration
1 Like
@geppino Hi lets see from your list;
- Use myrlyn
- Don’t use, not a good idea…
- Use myrlyn
- Desktop should take care of that… (It does on GNOME)?
- Do that at install? Depends if systemd-boot or grub, very quick from the command line for systemd-boot with
pblandsdbootutilcommands. - Cockpit does this
- Cockpit does this
- Desktop should take care of that… (It does on GNOME) as well as date/time?
1 Like
a) I’ve never heard about “myrlyn”. Because not installed I searched for it in … yes in YAST (installing software/packages) and I didn’t found it.
b) I usually install (brother) printer drivers with the brother tool (a script). It normally runs perfect, but sometimes there are problems. In this cases I useed the printer install routine in YAST. I have never used KDE for that. Is there really a KDE driver install suite?
c) Cockpit - I’ve never heard about this. I installed through YAST and … How to run it? No listed in KDE menu. From terminal as root:
# Cockpit
Wenn 'Cockpit' kein Tippfehler ist, können Sie command-not-found benutzen, um das Paket zu finden, das den Befehl enthält, z. B.:
cnf Cockpit
# cockpit
Wenn 'cockpit' kein Tippfehler ist, können Sie command-not-found benutzen, um das Paket zu finden, das den Befehl enthält, z. B.:
cnf cockpit
@geppino I use HP LaserJet, it needs plugins to operate, but since it’s a network printer it just appears…
I use the flatpak version as my user, so not the rpm version.
You need to install the cockpit-ws and run it as a web service.
https://cockpit-project.org/running and https://cockpit-project.org/running#tumbleweed
1 Like
My printer is network one too, but few years ago I was a network guest, I was able to connect the PC (LAN) and the printer, but not able to login in the rooter to identify the printer address. YAST helped me.
I don’t know, If there are flatpak versions for brother drivers, but I remember, you often suggest to maximal reduce third part apps, don’t you?
$EDITOR /etc/cockpit/disallowed-users
I installed the cockpit-ws and I followed the install instruction from cockpit web side
… but I don’t understand, why to install or de-install packages.
Apart this, I think, it is very dangerous to outsource the software management to a not economic controlled third part …
You missunderstood something. Cockpit is available in the official openSUSE repositories. And software management can be done via Myrlyn as explained.
@geppino what do you mean, that’s just some instructions on what to do on Tumbleweed and Leap?
Flatpaks are the norm as long as you look at installing as your user on the likes of MicroOS, Aeon and Kalpa. I run a number, which as my user doesn’t have the opportunity to mess with the system. Easy to recreate a user than a system 
Flatpak is a packaging format, like RPM. Flathub is a repository, but not the only repository.
Nothing’s been “outsourced” here, any more than you go to Packman for packages that aren’t able for legal reasons to be hosted on the official openSUSE repos (like patent-encumbered codecs).
What is Myrlyn? I can’t find it in repositories of Leap 15.6.
# zypper in myrlyn
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...
'myrlyn' wurde in den Paketnamen nicht gefunden. Fähigkeiten werden durchsucht.
Keine Anbieter von 'myrlyn' gefunden.
Paketabhängigkeiten werden aufgelöst...
Keine auszuführenden Aktionen.
you wrote “… as explained”
May I have overlooked something here?
I can really understand, how to use this cockpit.
What do I have to do, when I want to install i.e. Kontakt (KDE)?
When you have installed the proper Cockpit modules (cockpit-packages in this case) you can (un)install packages via Cockpit.
Ok. I realized: not yet available for Leap 15.6
The GUI seems the same of YAST .