On Nov 24, 2012, at 8:10 PM, Ryan Schmidt wrote: > One idea that occurs to me is modifying the compiler.blacklist syntax. For > example: > > "compiler.blacklist clang" would blacklist all versions of clang, as it does > now. > > "compiler.blacklist clang<318.0.61" would blacklist clang builds less than > 318.0.61 (cairo might use this). > > "compiler.blacklist clang>=421.11.66" would blacklist clang builds greater > than or equal to 421.11.66 (mpich might use this). > > "compiler.blacklist 421.11.66<=clang<444" would blacklist clang builds > greater than or equal to 421.11.66 and less than 444 (mpich might use this, > if whatever clang bug it hit is fixed in some hypothetical future clang build > 444).
Would the last example be easier to write, read, debug and document as key/value pairs over two line? compiler.blacklist clang<444 compiler.blacklist clang>=421.11.66 Regards, Bradley Giesbrecht (pixilla)
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
