Ian Wadham <[email protected]> writes: > On Friday 13 May 2011 12:27:01 pm Raphael Kubo da Costa wrote: >> Ian Wadham <[email protected]> writes: >> > What I guess Mathias and I really need is to declare a strong >> > *functional* dependency on OpenAL and SndFile, without clobbering the >> > build, but making sure that the packager or builder sees that something >> > is missing. How can that be done? >> >> On the build side, do you need more than marking it as an optional >> dependency so that it will be shown as not found when CMake lists which >> packages were found or not? >> > That depends on who reads the list of not-found packages and when ... > After all, the list *is* headed by the word "optional" in capital > letters ...
>From what I understand, the main concern is getting packagers to notice these new dependencies. They are much more likely to check the output than a normal user who is building from source. > On a scale of 0 to 9, between "optional" and "required", I would rate sound > as 7 or 8 in this case, but how can you tell CMake that? I thought your intention was to make OpenAL/SndFile optional dependencies in that it would still be possible to build kdegames without them. There is no way to tell CMake they are semi-required :) >> You can also mail the kde-packager mailing list and warn the folks there >> about these changes. >> > Good idea, I would like to do that. But is it a public KDE list? I do not > see it on https://mail.kde.org/mailman/listinfo/ No, it's not a public mailing list: https://mail.kde.org/mailman/listinfo/kde-packager. You can send a mail to it and wait for it to be approved by an admin, though. _______________________________________________ release-team mailing list [email protected] https://mail.kde.org/mailman/listinfo/release-team
