does cmake really need to blacklist macports-clang >= 3.8?
Ryan Schmidt
ryandesign at macports.org
Sat Dec 9 16:01:41 UTC 2017
On Dec 9, 2017, at 05:07, René J. V. Bertin wrote:
> René J.V. Bertin wrote:
>
>> This is not (directly) a dependency issue that affects the PortIndex so maybe
>> it's possible (and acceptable) to wrap the compiler.blacklist statement in a
>> test expression? I can figure out the former, the latter a bit less ;-)
>
> This seems to do the trick:
>
> if {!([catch {registry_active "cmake"}] == 0 \
> || [catch {registry_active "cmake-devel"}] == 0)} {
> foreach cv {3.8 3.9 4.0 5.0} {
> if {[catch {registry_active "clang-${cv}"}] != 0} {
> ui_debug "blacklisting macports-clang-${cv} because it might need us
> for installation"
> compiler.blacklist-append macports-clang-${cv}
> }
> }
> }
As far as I know, the port works as is, and it took a long time to get it that way. Why do you want to change it and risk breaking it again?
More information about the macports-dev
mailing list