Bug 463474

kdesrc-buildrc's documentation makes some claims about displaying progress, some more grand than others. But even the most conservative don't seem to hold in all situations.

This, I found at
https://docs.kde.org/trunk5/en/kdesrc-build/kdesrc-build/basic-features.html#build-progress

========
Showing the progress of a module build
--------------------------------------
This feature is always available, and is automatically enabled when possible. What this does is display an estimated build progress while building a module; that way you know about how much longer it will take to build a module.
========

And this is from
https://docs.kde.org/trunk5/en/kdesrc-build/kdesrc-build/features.html
========
* kdesrc-build will show the progress of your build when using CMake, and will always time the build process so you know after the fact how long it took.
========

While that's all apparently true for the **build**, it's far less true in other situations. Recently, while setting up kdesrc-build on a new system, I wanted to just check out all of the necessary sources, before I thought about starting to actually build anything. So, I ran it in `--src-only` mode:

========
$ ./kdesrc-build --src-only
Fetching remote changes to sysadmin-repo-metadata
Merging sysadmin-repo-metadata changes from branch master
Holding performance profile
========

<delay form="interminable">
That was the last thing it printed before starting its work. Cut to THIRTEEN+ MINUTES of absolutely no output whatsoever.

I could _see_ it working in the process list, or in a `top` display. But there was certainly no indication of that, from the terminal window where the process was actually _running_.

And then, finally, all at once when everything was finished, it dumped out:
</delay>

========
The following modules were updated but not built:
	kfilemetadata
	kactivities-stats
	kcalendarcore
	plasma-wayland-protocols
	kservice
	kholidays
	karchive
	syndication
	poppler
	kde-dev-scripts
	purpose
	kunitconversion
	kcontacts
	breeze-icons
	kxmlgui
	threadweaver
	polkit-qt-1
	kbookmarks
	kdoctools
	qca
	solid
	kwallet
	qqc2-desktop-style
	kdeclarative
	ktextwidgets
	phonon
	bluez-qt
	kitemmodels
	kcoreaddons
	extra-cmake-modules
	kdbusaddons
	kdnssd
	kparts
	knotifyconfig
	kwidgetsaddons
	kdav
	kglobalaccel
	kquickcharts
	networkmanager-qt
	kwayland
	kauth
	kconfig
	syntax-highlighting
	knotifications
	kidletime
	kirigami
	kdesrc-build
	oxygen-icons5
	kimageformats
	kio
	kdesu
	frameworkintegration
	phonon-vlc
	plasma-framework
	kpeople
	krunner
	kcrash
	kcmutils
	ktexteditor
	ki18n
	modemmanager-qt
	kplotting
	kwindowsystem
	kded
	kguiaddons
	kiconthemes
	attica
	baloo
	prison
	kitemviews
	kconfigwidgets
	kactivities
	sonnet
	kcompletion
	kjobwidgets
	kpty
	kapidox
	kcodecs
	knewstuff
	kpackage

:-)
Your logs are saved in file:///...
========

I know it took exactly 13m22s, in fact, because my zsh prompt times the execution of each previous command.

That's an awful long time to go with _no indication whatsoever_ that the command you've run hasn't gone permanently out to lunch.