Regarding GParted, I have been back and forth on that too, for my own fork. GNOME Disks does 99% of what it does. But gparted is so nice for that last 1% where you need some extra info.
I’ll leave some feedback there tonight. This is correct however we’ll need a small bit of transition code to maintain compat. Otherwise existing users are going to get the first run installer again unexpectedly
I know but didn't consider it mattering, because yafti is only used by people who rolled custom images (Small percentage) and it's all marked as alpha, so having transition code is kinda pointless.
Okay. Do we really want some messy code that looks for the old file and moves it to the new location though? Bluefin is ALSO alpha software. And they'll see yafti.yml every time it updates anyway.
in regards to gparted is one of those tools that generally isnt needed by most unless they need to do something specific so its something users can layer themselfs
This is about yafti's new config location. It's only used in custom images and in bluefin. Both are alpha.
Bluefin installations will currently see yafti every time they install the OS and every time yafti.ymlyafti.yml changes (that's how it's designed), i.e. when Bluefin changes default config.
I can certainly put in code that also looks at the old location but yikes that's messy for something that fixes itself after 1 Yafti appearance.