That point is especially for the userspace as this one is done on that base and therefore the essential problem for our first tryouts not working before to finalize the pre-alpha. But in general speaking: We need a working system-base before going into writing more compatible code added or replacing other parts. GCC will remain surely, but the focus is on LLVM for the moment as the current package is not fully clean implemented.

Generic: The core-repository in the future is only for BSD-parts and basics for the system. The extra-repository will include GNU-applications and as said other parts as it does today. HyperbolaBSD is therefore no GNU-oriented system and Hyperbola itself has no focus on GNU for the future. Hyperbola will always state its focus on the FSDG-principles as a free, libre and user-oriented system.

We are at the moment in further evaluation for llvm / clang: As said this takes much work for the moment on side of Coadde and Emulatorman. The reduction of packages is not the only part on my side doing / done as I also rework the way packages are lined up. Linear dependency trees support the work for llvm / clang as we perhaps may also end the 0.4.x-cycle after 0.4.5 and then start 0.5 for Hyperbola GNU/Linux-libre. This is not finalized but 0.5 will then also go into a restructuring for BSD-preparations and then after that for 0.5.x also eudev-removal as already stated before. Some packages vary back and forth but in general said: Clang / LLVM and GCC are here to stay, GCC and binutils then in extra for 0.5 and further.

There is no point to change that in special. Also ruby will stay so far.