On 03/11/2018 07:22 PM, Carlos E. R. wrote:
On 2018-03-11 15:00, Knurpht - Gertjan Lettink wrote:
Op zondag 11 maart 2018 13:31:00 CET schreef Carlos E. R.:
On 03/10/2018 01:36 AM, Carlos E. R. wrote:
Hi,
...
On boot, YaST had installed grub to /dev/sda4, overwriting the main system, ignoring my explicit orders to install on /dev/sda9
I don't understand this, YaST had this working on previous versions. Why write the code again?
The reasons for a complete rewrite of YaST have been explained. In short: YaST was writen in it's own language, resulting in the fact that both YaST and the coding language have to be maintained to stay up with developments. Rewriting in Ruby opens options for new developments/technical improvements.
But the translation was done and finished years ago.
You mean that maintenance is done on the original language, not Ruby, then translated again to Ruby?
Then the code is being redone from scratch in Ruby?
Ouch. That hurts.
Please, don't mix the conversion to Ruby with the rewrite of the storage stack (i.e. replacing libstorage and yast2-storage with libstorage-ng and yast2-storage-ng). They are completely different and disconnected things. The conversion to Ruby was done and finished years ago for the reasons explained by Knurpht above. The storage-ng effort is a current WIP and the reasons has been stated in several places (including this list regularly). One of the most recent communications is this article in news.o.o. https://news.opensuse.org/2018/01/09/future-tumbleweed-snapshot-to-bring-yas... Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org