How to announce new optional dependencies? [was: What KDE would like distributions to do]

[Luca Beltrame]

In data lunedì 21 marzo 2016 12:59:51 CET, Martin Graesslin ha scritto:

> How do you suggest this to work? The last time I run into the situation that
> I needed to add an optional dependency and tell distros about it, it failed

Could this be scripted when generating the pre-release (at Beta) tarballs by 
providing a list of dependencies? Or when dependency freeze is hit? This 
should go in tandem with one of your suggestions below.

> * we need better output from CMake (more structured storage of feature info
> -> xml?)

This one,  I mean.


-- 
Luca Beltrame - KDE Forums team
KDE Science supporter
GPG key ID: A29D259B
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/distributions/attachments/20160321/02dbccff/attachment.sig>