Version: git (using Devel) OS: Linux When kdesrc-build-setup prompts current list of modules (by this time, only quite a basic kde desktop setup, with no extras), it could download kde-build-metadata and offer to user all available modules at kde-git (and, if possible, handle dependecies while s/he checks what s/he wants). Also, maybe as a second step to checked modules, it could let the user select a branch or stick with master (or, else, any defaults kdesrc-build uses, as 4.8 is for qt by this time). Maybe it could display for each of those checked modules the next closest thing to a drop-down (though I don't know if such a thing would be easy to come up with in a char-based GUI) having all branches for that module as its options. Or perhaps, if such a drop-down isn't possible, it could be a nested list to show up. That'd be the best deal ever for building a user-fully-featured KDE desktop from source! Reproducible: Didn't try Expected Results: kdesrc-build-setup offering all available modules at kde-git (and possibly handling their dependecies while user checks modules) and, for each those checked, their branches for selection.
When I say it could download kde-build-metadata, maybe it'd actually be kde_projects.xml (which I've then -- curiously -- opened and figured out it's the whole list of kde git/svn projects and master and stable branches) or even both (since, snooping kde-build-metadata I found out it's probably more to handle dependencies) ... I'm sorry, I don't know kdesrc-build that well to tell, I only read somewhere what they supposedly would be/do and based on it.
For what it's worth I think this is a swell idea (in general, your request is a bit vague), but haven't found enough time to implement.
`kdesrc-build-setup` was deleted with this commit: https://invent.kde.org/sdk/kdesrc-build/-/commit/036f5092adc382e3cc0e4c5a4946b1dbcb10ec03 Use `kdesrc-build --generate-config` instead.