policy proposal : runtime only checks be non-fatal

[Alexander Neundorf]

On Thursday 07 January 2010, Rex Dieter wrote:
> There are an increasing number of cmake checks in core kde modules (as well
> as others), for items needed only at runtime (not buildtime).
>
> That is all well and good, but these often are not optional checks, which
> as a packager, I very much object to.
>
> Is there any sort of best-practice or policy for this kind of thing (yet)?
>
> If not, I'd propose runtime-only cmake checks:
> 1.  not be fatal for the build
> 2.  output/warning be made clearer that this is a runtime-only
> dependency (or the check be removed altogether).
>
> 2 cases of this come to mind,
> kdebase-workspace for kdebindings/python (circular deps are bad, mm-kay)
> amarok for qtscriptgenerator

If it's really not required at buildtime, i.e. not even some install location 
or something, maybe we don't need to check for it...
But, well, otherwise we'll build/install e.g. PyQt stuff but then you won't be 
able to actually run it. I guess that's the motivation why to check for it.

Not sure.

Alex