As of today PM said they do not want any YaST in SLES 16.
On Leap side, I'd very much like to keep at least the YaST Software for additional package installation, and ensure that migration from Leap to SLES is covered. That might require additional tool for migration which doesn't use shared YaST libraries.
Metadata Update from @lkocman: - Issue assigned to lkocman
https://hackweek.opensuse.org/24/projects/new-migration-tool-for-leap
https://hackweek.opensuse.org/24/projects/yqpkg-bringing-the-single-package-selection-back-to-life
Next step should be probably to drop all of yast, and submit https://github.com/openSUSE/migration-tool and https://github.com/shundhammer/yqpkg/issues/1 to Factory and later Leap.
Stanislav just mentioned releated drop of packages-18n.
We did agree with Dimstar that it might simply make sense to drop yast related patterns from Leap 16, if we talk about handful of packages. And perhaps to simply add yqpkg into some enhanced desktop pattern or similar.
Factory would still keep yast patterns and probably would add yqpkg there.
https://build.opensuse.org/request/show/1236143 https://build.opensuse.org/request/show/1236177 https://build.opensuse.org/request/show/1236176
For now I close the request. I'd reopen it In case we need more yast libs or tools. But then I'd prefer individual issues, with particular user story that can't be solved without cockpit or builtin tools in GNOME and KDE.
Metadata Update from @lkocman: - Issue close_status updated to: Completed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.