YaST3 project (unofficial)

[jsulig]

@hendersj

This is IMHO a good reason to adopt tools that are more commonly used across distributions - so knowledge those who don’t use SUSE/openSUSE distributions have isn’t useless when switching.

YaST does not exclude other means of managing the system, it just provides one additional way.
Just want to correct this point, not argue about the decision.

[guoyunhe]

@hendersj

This is IMHO a good reason to adopt tools that are more commonly used across distributions - so knowledge those who don’t use SUSE/openSUSE distributions have isn’t useless when switching.

One goal of MaST (renamed from YaST3) is to support more distributions, e.g. Debian/Ubuntu/Arch. From a maintainer’s point of view, supporting more distros makes a project more likely to survive: much bigger user base and contributor base.

[knurpht]

@hendersj

That works in theory if all you ever use is SUSE distributions. But if you’re coming from any other Linux distribution, having to learn another tool for system management is a barrier to adoption

Somewhere in 2008-2010 I wrote some oneliner to find all the files changed / created between before and after using some YaST module. Reason was, that I ( in hindsight rightly ) assumed that could help me to / with work on other distros, and it did. It brought me even more, like f.e.understanding the whole reasoning behind the move from /etc to /usr/etc and appreciate that based on understanding what this solved.

[hendersj]

That’s a good goal, and it will be interesting to see how it goes for you. I’ll definitely be following along.

[deano_ferrari]

Following consultation with the OP, he wished to notify that this project is now called MaST, and those that are interested can follow it here:

guoyunhe/mast · Discussions