Some small remarks:

The broken language and time screen seems to be a QEMU issue indeed. We are mostly testing on VirtualBox and sometimes on VMware, but so far none of use tried it on QEMU.

The “Administrator” checkbox on the user setup page just configures sudo for the chosen account.

The “Configure System” item at the end of the installation will point to an “advanced settings” page in the future, where you can configure everything through an embedded Arxin instance. The idea is to allow even totally unexperienced users to do a basic install, and users with more experience can tweak the installed system after the basic installation has been finished, of course this is a optional step.

Plymouth is basically working but not ready yet to be included on the LiveCD, we are waiting for more more “out of the box” stability and better support from the drivers.

The /etc/hosts and MODULES array issues are interesting… Because these were some of the first modules i wrote back then, and they worked fine since alpha1. Maybe our recent move to larch7 is the cause here, or someone just broke it™ on the way. It could be even fixed on one of the newer devel images…

About the order of the repos: It is intended like this. Normally we are not providing any packages that are already in [core], but sometimes we “override” some packages from [extra], especially when a new major release of KDE is in our testing repo.

About the comments from gtklocker and FSF: You know the verdict about opinions? And what Pierre said is true, we already talked about that and so far i see no real solution for the “bug reporting behaviour” of some users. We do not link to the Arch bugtracker for example, not even in the KMenu or other places. All in all, i guess we will need our own “platform” at some point in time, as Arch is not really the distro for what we want to deliver. Not technically (it is a fine platform, one of the finest) but more in terms of philosophy, so i definitely agree with you here.

Well, we’ll see what the future has in petto Thanks again for the review…

Personally I see this as a big fail, to accept MS Eula when installing GNU/Linux distribution. This is like from a horror movie

Chakra devs should consider using another fonts, why use stupid MS fonts when they apply EULA for it? IMO This has nothing to do in a standard install of GNU/Linux distro.