Check out that link. I've used its instructions, and you can get most of the way there following what they have to offer. Compiling is challenging and a bit time-consuming, but it's fun and once you do it, you gain pretty much complete control of your program list, although it's always with a word of caution: Source code from unverified sources could potentially harm your computer!
The only tip I'd have is that almost always, when a program is saying "dependency missing", then they mean "dependencyname-dev" rather than the dependency itself. So, for example, if I try to compile VLC, it may say that gstreamer-plugins-good is missing, even if you have it on your computer. That's because you need gstreamer-plugins-good-dev to do the compiling.
Unfortunately, because of the different developers behind each individual project, sometimes the name game isn't quite that easy, and you'll find they ask for a package that's not in the repository. Often it's because it's under a different name, so you have to do searches for the different names and hopefully after installing different -dev packages that relate to the program, you'll get there.
Once you get the hang of it, it's not too much trouble. But the first couple of times, it can be tempting to give up because it's finicky to find the right dependencies for some programs (VLC being a great example -- it does so much you need to install half the flipping repository to compile it!)
...loving life for Christ's glory...