You have to replace these lines with something similar to this (change libaacs to libgcrypt everywhere). Then run autoreconf -iv (you must have autoconf installed). It will create a new ./configure script which will work if you did everything correctly.
Refer to documentation.
It’s just generally faster to use the terminal if you know what you’re doing.
It's also true for other distros. Not because they have poor GUI tools but because CLI is faster than GUI if you know what you are doing.
Be careful if you buy a Samsung 8x0 SSD. They have long standing bugs that may cause data loss. They are worked around in the kernel, however you have to ensure that the workaround for your particular model exists in the kernel version you use.
Glibc preserves backward compatibility, so if you build against the oldest version you want to support, the resulting binary will work with newer ones.
However that's definitely not what I recommend to do. Better learn packaging and build native packages for distros you are going to support. OBS can make this a bit easier (if your software is FOSS), but any modern CI will also do the job.
Isn't that video stream already compressed? Or you want to convert it using another codec/bitrate?
LOL, all Linux vendors = Red Hat.
All generalizations are false.
I don't know, however this is impossible to understand what's wrong with your fonts.
git config core.sshCommand 'ssh -i <path to desired key>'
The biggest problem that I see on this screenshot is that it is a compressed JPEG.
Technically, you always use a username, however in case of Gitlab that SSH username is always git. When an SSH client connects to server, it offers an authentication method. Gitlab accepts that method only if it is a publickey and the fingerprint of the offered key maps to the known Gitlab user.
Congrats, you are very lucky. But try to survive couple of version upgrades before recommending it to noobs.