@per: looks good to me, i agree understanding the bare minimums at first to build your own image will help with a lot less bricking and keep the fear out of peoples minds that development is a scary brainyack thing only geniuses are capable of, also leading to more improvements and releases, just beware with other peoples builds you never know if they dropped in a backdoor
Edit: Looks like it's got you using the current master branch, so yeah that's the most current available source. It may be better to use a snapshot if you're developing, or release if you want guaranteed stability.
You just make your changes, save the config, and build again. It doesn't have to recompile the entire toolchain so that save a lot of time. Successive compiles are much faster than the first.
If you star it, it's included, so yes enabled by default, if it's an M, it's an .ipk that you can transfer to your device and install with opkg.
I need only master branch - I'm not a developer, I just need support for specific hardware, which is not in stable yet.
Also, I don't know how to get specific snapshot or release source (can not think what to google or what exactly to look for to get answer). Can you teach?
That is not what I had in mind. It is possible to quickly get/update files or I should just run all commands again from section "Get the LEDE source code:" from that quickstart page (will not take much time, but maybe this is not very correct solution).
Edit: Tried that and it won't clone source again, because such dir already exists. Next ./scripts/feeds commands are working, but they won't update existing main source files. Update: Well, "git pull" is the answer.
This seems like a life-skill i should try and develop... might just not be me who sometimes complicates things. This was way better. I'm no coder, but this is a good summery. TLDR, or what you want to call it. Thanks