[104033] trunk/dports/kde/kdepim4-runtime/Portfile

[Ryan Schmidt]

On Mar 14, 2013, at 12:40, Lawrence Velázquez wrote:

> On Mar 14, 2013, at 9:32 AM, Nicolas Pavillon wrote:
> 
>> After testing the blacklist command, one thing I could not really understand is that putting 
>> compiler.blacklist  apple-gcc-4.2
>> in the Portfile, and then running 
>> sudo port -ds install <port> configure.compiler=apple-gcc-4.2
>> still selects apple-gcc-4.2 as the compiler, even though it is indicated as not working. Is it intended behaviour?
> 
> This is expected. The black/white/fallback lists are used to determine the default value of configure.compiler. Once configure.compiler is changed from the default, they no longer have an effect.

I found it a little unexpected too, but:

>> It this is intended, I don't find ideal to let the user go crash in the errors even though it was indicated in the Portfile that it should not be done, and without any visible warning.
> 
> Sure, but it's also arguable that passing configure.compiler on the command line is intended as a debugging measure meant for explicitly overriding the portfile; as such, the portfile should not interfere with it.

I came to that conclusion too. Still, it might be helpful if MacPorts base were to ui_warn about using a compiler that the portfile has disallowed.