@kev Nice! Congrats! It's funny as I made a few posts on pull requests recently. Always something new to learn!
That is a nasty environment to have to build all of that just to run on your machine.
- No repo or build available for your OS
- Bug that was patched in the source code but not in an available build
- Change the configuration of the software that utilizes build flags (can exclude support for old CPUs for improved performance)
- Apply a patch to the source code to enable a specific use case on your machine (expose functionality that may be useful to you)
Just to name a few :) definitely not for easy app management.
@kev Nice! Now you can get into the fun of branching strategies and pick a side of the merge vs rebase war!
A lot of doors opens knowing anything, and in the case of git, control of what, how and when was something done to, at some point, take action or just knowing the history and context.
If I may have my unsolicited advice, I think the next config step is add signed commits to your git workflow using PGP/GPG
The above suggestion is to add to the mix the who did that piece (for sure).
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.