diff options
1 files changed, 5 insertions, 5 deletions
| -rw-r--r-- | src/blog/taming-the-fun-too/index.du | 10 |
diff --git a/src/blog/taming-the-fun-too/index.du b/src/blog/taming-the-fun-too/index.du index 018f6ae..f6bcf41 100644 --- a/src/blog/taming-the-fun-too/index.du +++ b/src/blog/taming-the-fun-too/index.du @@ -13,7 +13,7 @@ However, at that time I was a bit softened by my growing pains with Fedora, the So, about a month later I bit the bullet, and installed it on my main computer. It has now been a tad more than a year later and I can comfortably say: {i a lot could go wrong...} -<br/> +{br} In the same way that a distro is made to solve a certain problem, every distro introduces a fundamental flaw in it's design. Ubuntu solves the "it's too complicated" problem, but introduces issues with performance. Arch solves "my packages are too old and what I need isn't there" issue, but introduces "my packages are too new and something just broke". @@ -21,7 +21,7 @@ Then there's Funtoo. You might reason, since it's a fork of Gentoo, it's big fla The distribution is a lot smaller than it's big brother so a lot of stuff, understandably, cannot be tested. However, the real kicker is that package ebuilds{fn Files with instructions and settings for the package manager (portage) on how to build a specific package} are generated in a different way from Gentoo. This often means that using a Gentoo ebuild will make the problem even worse, but sometimes it does work out. -<br/> +{br} The first such problem child was QtWebEngine. As the name suggests, it gives the ability for graphical applications, made with the Qt framework, to render webpages. I don't {i need} it for my setup, but there are a couple of useful programs that required it. @@ -32,7 +32,7 @@ A fairly deep dive into different forums led me to the wondrous conclusion that After {i much} tweaking and trying, I found out there just wasn't enough memory, the package needed at least 32 GiB (including swap) of memory for a successful compilation... D'oh! And here comes the really bad part: I had setup a swapfile of adequate size! However, as it turned out, in the configuration I tried loading it before loading the drive it was stored in... {b Double D'OH!!} -<br/> +{br} Then came the big boss: python. Now, I wasn't planning on doing any software development with it, but as it turned out, other people had, so certain packages had building issues. And what was the exact issue you might ask? @@ -45,7 +45,7 @@ Usually there are solutions to such situations, but I kid you not, I had tried { This time, there isn't even a solution, I just made sure to never upgrade these packages again. Which proved problematic, since these packages were important and over time other stuff broke, but that wouldn't be relevant for long. -<br/> +{br} Not too soon after, armageddon struck: glibc, GNU's C library. All I wanted to do was try out Ungoogled Chromium, but not as a flatpak. The only thing standing in the way was the requirement of "glibc 3.4.29", while all I had was 2.70.0. @@ -65,7 +65,7 @@ A sanity check override and a package downgrade later, {i it wasn't...} Yes, my system was broken. Very broken. So broken in fact, portage wasn't working, so un-downgrading was not an option. And, of course, booting successfully my machine up ever again wasn't an option either... Thank goodness for {url Timeshift;https://github.com/linuxmint/timeshift}'s system restore functionality or I would've had to rebuild my whole system. -<br/> +{br} There are {b a lot} of other situations in which Funtoo's package difficulties and my sheer incompetence have led to wasted time and broken stuff, but these are the main ones that stand out in my mind (or more accurately, the ones that I still remember). Nowadays I use the distro in a much smarter fashion, with a much tighter grip. |