3 ms·
To be fair, I only use it on servers; I could imagine having to compile Gnome or KDE is a little more bothersome. I feel the same about Gentoo, but my approach
by loudmax 12y ago
To be fair, I only use it on servers; I could imagine having to compile Gnome or KDE is a little more bothersome.
I feel the same about Gentoo, but my approach to desktops and servers is the opposite. If my laptop or desktop breaks during a Gentoo upgrade, it's an interesting learning experience (after much gnashing of teeth and shaking of fist). If a server breaks during an upgrade that's a business impacting outage. So I prefer to run Red Hat or CentOS on servers despite distinct lack of awesome latest packages.
I never bothered with a Gnome or KDE desktop. Compiling XFCE, Firefox and Chromium takes long enough.
- vezzy-fnord 12y agoPortage supports installing binary packages from a binhost, as well. Most large packages (Firefox, Chromium, LibreOffice, etc.) have precompiled versions that follow the naming convention of $SOURCEPKGNAME-bin.
- valarauca1 12y agoKDE takes about 30 hours to compile on my core i7-4790k even threading it out to all 8 threads.
- OGC 12y agoHeh, it took me about 2-3 days on a PIII 450 mhz once.
- jinzo 12y agoInteresting. I'm running a mix of i3wm and some Gnome apps on a relatively old Intel P8700 powered laptop and the only compile pain points are browsers and libreoffice (I ended up using the -bin package).
- andmarios 12y agoThat is too long. On my i7-3630QM laptop it takes about six hours or less. I haven't seen KDE (with almost all use flags enabled) take 30 hours since 2006 on my Pentium 4 and I have emerged every major and minor update since then. Even on Pentium 4 I think the usual emerge duration was around 18 hours most of the time.
- valarauca1 12y agoI think I maybe counting KDE's dependencies into that figure. Not just KDE alone.