If you use eix, you must run the command eix-update each time portage syncs to remote repositories (for instance, when you run emerge --sync) in order to have an updated cache to search. In this video, I show you how to use #Gentoo's postsync hook functionality to easily automate this process:
Gentoo's emerge command has the built in --search option for searching for packages, but a greatly superior tool exists in the portage ecosystem: eix. Check out this video to learn how to use eix, the faster, better-formatted package search utility for portage:
Keywords, in #Gentoo #Linux, are used by portage to determine if an ebuild will be compatible for a given CPU architecture, and whether or not the package that ebuild applies to will be stable on said architecture. In my newest video, I go over how to use the package.accept_keywords file to mask and unmask packages on the basis of their keywords:
New video coming out later this evening. It'll be the first #Gentoo video in a while!
Using ccache can greatly speed the process of compilation when you need to compile the same version of a package multiple times (on #Gentoo #Linux, a good example of this is when testing out USE flags). In this video, I discuss how to install and configure ccache to work with portage.
I've been building Flóðgátt, a replacement streaming API server for Mastodon. The goal is to cut RAM usage and make hosting an instance that much cheaper.
So far, we've cut RAM for the streaming server of an empty instance by ~94.2%
The next task is to make sure that lower RAM usage can scale without other issues (e.g., CPU).
To do that, I need a test server with enough connections to see how Flóðgátt performs under load.
That's where y'all come in: can you please follow @codesections ?
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.