I honestly have only passing knowledge of it, but my understanding is that Open Build Service is more for sharing software whose source code you are allowed to distribute. If you aren't looking to distribute at all, the solutions other users suggested might be better.
There's also a way to create an APT repository entirely on your own system, without a web server, which I haven't tried myself, but a DuckDuckGo search found this: https://help.ubuntu.com/community/Repositories/Personal
Unsure if this is what you're looking for, but I've seen some FOSS projects use https://www.makedeb.org/ and https://openbuildservice.org/ to create public Debian repos.
Moderately "leave me the fuck alone", and usually indifferent but a number of things can swing me into extreme silliness.
Unfortunately, the state of Android music players is not great. Currently I have two FOSS music players installed: Metro Music Player (the F-Droid version of Retro Music Player) and mucke. mucke has a ton of really cool features that improve the shuffle experience but it's actually worse than most apps at pulling album art. Retro/Metro has beautiful UI, and has pretty good features for customization, but lacks the cool features mucke has and is less stable. Both have more than one annoying bug, but it took me a while to find music players that had this few dealbreakers.
chmod'd all my home directory's files and folders recursively. First to 600, which prevented me from listing any folders, then to 700, which broke a few programs, then to 755, which broke ssh.
Yeah, basically. makepkg automates the process of creating an Arch package, and while usually that involves compiling source code, sometimes it just means converting proprietary software that has already been compiled into a different format.
In that case makepkg isn't compiling anything, it's just packaging the existing binaries so that they can be more easily installed and recognized by your package manager.
Open-source software is distributed primarily as source code in a human-readable programming language. Computers can't actually read these programming languages directly; they need to be translated into the machine language of their CPU (such as x86_64). For some languages, like Python, code can be "interpreted" on the fly; for others, like C, programs must be "compiled" into a separate file format. Additionally, most programs consist of multiple files that need to be compiled and linked together, and installed in certain folders on your system, so the compiler and additional tools work to automate that process.
Most users of Linux rarely if ever have to compile anything, because the developers of Linux distros, and some third parties like Flathub, curate collections of (mostly) open-source software that has already been compiled and packaged into formats that are easy to install and uninstall. As part of this process, they usually add some metadata and/or scripts that can automate compiling and packaging, so it only requires a single command (makepkg on Arch, dpkg-buildpackage on Debian.) However, some newer or more obscure software may not be packaged by your distribution or any third-party repo.
How to compile depends on the program, its programming language and what tools the developers prefer to use to compile it. Usually the README file included with source code explains how to compile the software. The most common process uses the commands ./configure; make; sudo make install after installing all of the program's dependencies and cd-ing to the source code directory. Other programs might include the metadata needed for something like makepkg to work, be written in an interpreted language and thus require no compilation, or use a different toolchain, like CMake.
I hope these shots aren't a good representation of the whole episode, because if they are, it's a 15 minute scene of L'Ak and Moll on a planet followed by 35 minutes of close-up shots of Rayner
Last time I used Elementary OS, it was great if you were only using the official apps, with insane degrees of polish, but things like LibreOffice were surprisingly hard to configure the way I wanted. That was a while ago, though.
There was still Wine, and PlayOnLinux helped further, but when I looked for a game I wanted to play on WineDB, there was no guarantee it even had an entry, and if it wasn't listed as "platinum", the chance of you experiencing any reported issue was very high.
Not to mention, playing Steam games that weren't native was an impossibility.
Thankfully I was more of a console gamer at the time, and I got a lot of enjoyment out of the few games that received Linux ports - like Team Fortress 2!
Can you be more specific about what happens when you reboot? Does it go to blank screen, a blinking cursor, or just shut itself off? Does the operating system start and just get stuck somewhere in the boot process, or does it not even get that far?
I think F12 is the BIOS key, if that helps. If it attempts to boot the operating system, you can press one of the arrow keys to see the boot log.